On Wed, Sep 17, 2014 at 4:02 PM, Diamond <[email protected]> wrote: > On Mon, 15 Sep 2014 14:51:56 -0400 > Rich Freeman <[email protected]> wrote: >> >> In general you want each commit to represent a single "change." That >> might be a revbump in a single package, or it might be a package move >> that involves touching 300 packages in a single commit. > > Is it right that you are going to move portage packages to > git/github/..?
The intent is to move to git. Git is an scm. Github is a service that hosts git repositories with some other value-adds. There is interest in mirroring gentoo-x86 on github to help entice more to contribute (assuming they like working with github), but the nature of git makes it very easy to mirror a repository on as many sites as you care to. That is one of the reasons that it is so popular with FOSS. > How are you going to make "revbump" with git? With cvs a revbump is: cp foo-1.ebuild foo-2.ebuild cvs add foo-2.ebuild cvs commit With git a revbump is: cp foo-1.ebuild foo-2.ebuild git add foo-2.ebuild git commit (I left out changelogs, repoman, etc, since there is no change with any of these, and I left out syncing the git repo.) There really is nothing new here. > Especially > if you need to see the diff between packagename-0.1-r1 and > packagename-0.1-r2 ebuilds? Git doesn't do this by default and it > will might be a nightmare to compare such revbumps by hand. > cvs doesn't do anything to compare the contents of different files. So, there really is no loss here. -- Rich
