From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: RFC: better policy for ChageLogs
Date: Thu, 02 Jun 2011 09:09:04 +0400 [thread overview]
Message-ID: <1306991344.4416.37.camel@tablet> (raw)
In-Reply-To: <BANLkTi=cVYzrLnwdY0dJyk=mpOzwK6DRcQ@mail.gmail.com>
В Срд, 01/06/2011 в 19:37 -0400, Matt Turner пишет:
> On Wed, Jun 1, 2011 at 7:29 PM, Jorge Manuel B. S. Vicetto
> <jmbsvicetto@gentoo.org> wrote:
> > To be clear I support the goal to move our tree to git.
> > However, I'd like to point out that simply moving to git will leave us
> > in the same state.
++
ChangeLog files are text to be distributed to our users so they are
completely independent of vcs we use.
> > Assuming everyone agrees that git is far more useful
> > than cvs to check for changes in the tree, a simple but important issue
> > remains: the plan is to move the "development tree" to git, but to keep
> > the rsync mirrors for users. So the "move to git" doesn't fix the issue
> > for users or developers using an rsync tree.
>
> Temporarily or permanently?
>
> One of the huge benefits in using git would be really fast emerge
> --syncs. Not having some kind of system for migrating users to git
> seems like a lot of the benefits are lost.
Is git faster then rsync? I've never done any checks but it'll be
surprising if it will. Another useful feature of rsync is --exclude that
allows some categories to be excluded (for size and speed efficiency),
e.g. my servers don't need kde-* and games-*. Also taking into account
that we use portage tree on embedded devices where again both size and
speed really matters it looks like the answer on your question is
"permanently".
--
Peter.
next prev parent reply other threads:[~2011-06-02 6:04 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-17 10:32 [gentoo-dev] Council May Summary: Changes to ChangeLog handling Petteri Räty
2011-05-20 10:19 ` Mart Raudsepp
2011-05-30 12:03 ` Peter Volkov
2011-05-30 12:23 ` Ulrich Mueller
2011-05-30 18:07 ` William Hubbs
2011-05-30 17:52 ` Michał Górny
2011-05-30 21:55 ` Brian Harring
2011-05-30 22:05 ` Common sense in [gentoo-dev] (was Council May Summary: Changes to ChangeLog handling) Andreas K. Huettel
2011-05-30 22:14 ` [gentoo-dev] Re: Common sense in " Diego Elio Pettenò
2011-05-30 23:38 ` Common sense in [gentoo-dev] " Brian Harring
2011-05-31 0:01 ` Ângelo Arrifano
2011-06-01 15:08 ` RFC: better policy for ChageLogs (was: Re: [gentoo-dev] " Peter Volkov
2011-06-01 15:15 ` [gentoo-dev] Re: RFC: better policy for ChageLogs Markos Chandras
2011-06-01 15:27 ` Samuli Suominen
2011-06-01 15:34 ` Ciaran McCreesh
2011-06-02 11:21 ` Jorge Manuel B. S. Vicetto
2011-06-01 15:39 ` Andreas K. Huettel
[not found] ` <BANLkTimgHYKnfbeQJpq829YBeE-5Yz=aEg@mail.gmail.com>
2011-06-01 16:24 ` Andreas K. Huettel
2011-06-01 19:50 ` Nirbheek Chauhan
2011-06-01 23:29 ` Jorge Manuel B. S. Vicetto
2011-06-01 23:37 ` Matt Turner
2011-06-02 5:09 ` Peter Volkov [this message]
2011-06-02 7:29 ` Duncan
2011-06-02 7:40 ` Eray Aslan
2011-06-02 11:20 ` Patrick Lauer
2011-06-02 11:05 ` Nirbheek Chauhan
2011-06-02 11:10 ` Ciaran McCreesh
2011-06-02 14:43 ` Rich Freeman
2011-06-01 15:30 ` Nathan Phillip Brink
2011-06-01 16:44 ` Duncan
2011-06-01 22:59 ` Rich Freeman
2011-06-01 23:21 ` [gentoo-dev] " Diego Elio Pettenò
2011-06-01 23:29 ` [gentoo-dev] " Dale
2011-06-01 23:40 ` Jorge Manuel B. S. Vicetto
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1306991344.4416.37.camel@tablet \
--to=pva@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox