Gentoo Archives: gentoo-dev

From: Peter Volkov <pva@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] Re: RFC: better policy for ChageLogs
Date: Thu, 02 Jun 2011 06:04:24
Message-Id: 1306991344.4416.37.camel@tablet
In Reply to: Re: [gentoo-dev] Re: RFC: better policy for ChageLogs by Matt Turner
1 В Срд, 01/06/2011 в 19:37 -0400, Matt Turner пишет:
2 > On Wed, Jun 1, 2011 at 7:29 PM, Jorge Manuel B. S. Vicetto
3 > <jmbsvicetto@g.o> wrote:
4 > > To be clear I support the goal to move our tree to git.
5 > > However, I'd like to point out that simply moving to git will leave us
6 > > in the same state.
7
8 ++
9 ChangeLog files are text to be distributed to our users so they are
10 completely independent of vcs we use.
11
12 > > Assuming everyone agrees that git is far more useful
13 > > than cvs to check for changes in the tree, a simple but important issue
14 > > remains: the plan is to move the "development tree" to git, but to keep
15 > > the rsync mirrors for users. So the "move to git" doesn't fix the issue
16 > > for users or developers using an rsync tree.
17 >
18 > Temporarily or permanently?
19 >
20 > One of the huge benefits in using git would be really fast emerge
21 > --syncs. Not having some kind of system for migrating users to git
22 > seems like a lot of the benefits are lost.
23
24 Is git faster then rsync? I've never done any checks but it'll be
25 surprising if it will. Another useful feature of rsync is --exclude that
26 allows some categories to be excluded (for size and speed efficiency),
27 e.g. my servers don't need kde-* and games-*. Also taking into account
28 that we use portage tree on embedded devices where again both size and
29 speed really matters it looks like the answer on your question is
30 "permanently".
31
32 --
33 Peter.

Replies

Subject Author
[gentoo-dev] Re: RFC: better policy for ChageLogs Duncan <1i5t5.duncan@×××.net>
Re: [gentoo-dev] Re: RFC: better policy for ChageLogs Eray Aslan <eras@g.o>