From: Ryan Phillips <rphillips@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Viability of other SCM/version control systems for big repo's
Date: Wed, 21 Dec 2005 23:22:52 -0800 [thread overview]
Message-ID: <20051222072252.GA10469@trolocsis.dyndns.org> (raw)
In-Reply-To: <dda83e780512212313r369555d3u9b7a021aab66040d@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1434 bytes --]
* Bret Towe <magnade@gmail.com> [2005-12-21 23:16]:
> On 12/21/05, Donnie Berkholz <spyderous@gentoo.org> wrote:
> > Donnie Berkholz wrote:
> > > I know some of you have done research on how gentoo-x86 converts over to
> > > other systems besides CVS such as SVN, arch, etc. But I can't find the
> > > info anywhere in my archives.
> > >
> > > Could whoever's got it, post it?
> > >
> > > I'm particularly interested in hearing about CVS, SVN, mercurial,
> > > bazaar, darcs.
> >
> > I've downloaded a copy of the gentoo-x86 repo and will run tests myself.
> > Please advise me as to exactly which tests you would like to see, beyond
> > whatever I feel like doing.
>
> might i also suggest testing out git along with the above listed?
> since i dont know git well enuf or what exactly are requirements of
> a gentoo dev ill just point to some documents
> tutorial can be found here:
> http://www.kernel.org/pub/software/scm/git/docs/tutorial.html
> and documention here:
> http://www.kernel.org/pub/software/scm/git/docs/
I know that some people have big reservations on distributed SCMs, but
why not switch to a distributed format, and cherry pick from other
developer's (and users) repositories?
Git allows for pushing to a centralized server, so it still 'works' in
a similar sense of committing changes to CVS.
cg-branch-add gentoo-main git+ssh://user@someplace/
cg-push gentoo-main
-Ryan
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2005-12-22 7:25 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 19:44 [gentoo-dev] Viability of other SCM/version control systems for big repo's Donnie Berkholz
2005-12-19 20:04 ` Ciaran McCreesh
2005-12-19 20:20 ` Mike Frysinger
2005-12-19 21:17 ` Patrick Lauer
2005-12-19 21:23 ` Ciaran McCreesh
2005-12-19 21:47 ` Patrick Lauer
2005-12-19 21:38 ` Fernando J. Pereda
2005-12-19 21:55 ` Peter Johanson
2005-12-19 22:35 ` Chris Bainbridge
2005-12-20 0:17 ` Kalin KOZHUHAROV
2005-12-20 0:31 ` Ciaran McCreesh
2005-12-20 3:07 ` Chandler Carruth
2005-12-23 19:33 ` Paul de Vrieze
2005-12-23 21:36 ` Ciaran McCreesh
2005-12-27 16:03 ` Paul de Vrieze
2005-12-21 20:54 ` Donnie Berkholz
2005-12-22 7:13 ` Bret Towe
2005-12-22 7:22 ` Ryan Phillips [this message]
2005-12-23 19:34 ` Paul de Vrieze
2005-12-23 20:38 ` Spider (DmD Lj)
2005-12-29 13:29 ` Luca Barbato
2005-12-29 3:39 ` Luca Barbato
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=20051222072252.GA10469@trolocsis.dyndns.org \
--to=rphillips@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