Re: [gentoo-dev] Gentoo git workflows and the stabilization/keywording process

[Rich Freeman]

On Fri, Sep 19, 2014 at 10:25 AM, hasufell <hasufell@g.o> wrote:
>
> That is pretty easy and takes you ~20s for a keyword merge. What's the
> problem?
>

Agree.  Also, there was a comment that git pull is much slower than
cvs.  While it is true that git does refresh the whole tree all the
time, it is FAR more efficient at doing this than CVS, since the local
and remote repositories can use a single hash to determine where each
stands relative to the other, and the COW mechanism applies to
directory trees so when making comparisons git does not need to
traverse the full depth of the tree for every branch.  A cvs update on
the entire tree is basically an independent synchronization of every
file in the tree.  Also, by refreshing the entire tree you also catch
any repoman errors that might result from commits to other packages
that you didn't have visibility to when refreshing only a single
package in cvs.

I wonder if it would make sense to set up a practice git tree
somewhere so that people can try working together on workflows/etc.
We can clone a migrated tree (I have one from a few days ago on
github).

I'm not super-familiar with github organizations, but if it is easy to
grant everybody in the gentoo organization access to a migrated tree
we could do that, and host it in the organization.  I don't care where
we host the tree - I just don't have anything set up personally.

--
Rich