Migrate to GitHub

• 

  Boppan

  Posts 70

  Joined: Mon Aug 26, 2019 10:14 pm

  Sun Dec 05, 2021 1:21 pm

  dunkaist wrote:Here are questions and issues to be addressed if moving to git.
  

  1. Unlike svn revision numbers, git hashes are not increasing numbers.
     • This creates navigation difficulties for pages like history of builds.
     • It becomes harder to binary search prebuilt images.
     • It is harder to tell if the commit c0ffee is newer than the commit deadbeef.
  2. Git hashes are longer than svn revision numbers, UI fixes may be needed (at least on the blue screen).
  3. Autobuild scripts operate on svn revision numbers, and are to be updated to work with git hashes. Some scripts are written in perl.
  4. There are existing references to svn.
     • In source and documentation files.
     • In board posts.
  5. There is sf18.13 that returns svn revision number.
     • And maybe programs using it, who knows.
  6. Current setup uses svn keywords and properties, e.g. Revision and eol-style. How to provide this functionality with git?
  7. WebSVN should be replaced.
  8. Existing svn tags and branches should somehow be moved to git.

  1. We can continue maintaining revision number (starting from the latest SVN commit) - one file and it's done.
     • Solved if we use revision number.
     • Solved if we use revision number.
     • We always can append revision number to a commit message using git hook.
  2. Solved if we use revision number.
  3. I'll take care of the scripts.
  4. The more we wait the more references we have.
     • With revision system we can leave it, just replace SVN by Rev. in places that need it.
     • The same for board posts.
  5. Not a problem if we maintain revision number.
  6. Havent checked how SVN does it, but I think we can create symple script that does this instead of svn.
  7. As mentioned, there are similar systems for git, but IDK how difficult it will be for server maintainers.
  8. I'll take care of it, it's big but essentially simple work TMK.

  Switching to git may give us lots of opportunities, starting from smaller repo size and simpler environment for new developers (most of newbies start from git IMO) up to being able to move to GitHub.
  
  Do we have any other problems with switching to git? If no, I'm ready to start it incrementally.

  • Quote

  https://magomed.org