public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stuart Herbert" <stuart.herbert@gmail.com>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] overlay support current proposal?
Date: Fri, 31 Mar 2006 09:16:17 +0100	[thread overview]
Message-ID: <b38c6f4c0603310016m1cf9749dp7d5843860c70e4e3@mail.gmail.com> (raw)
In-Reply-To: <20060330185410.GE1688@vino.zko.hp.com>

Hi Aron,

On 3/30/06, Aron Griffis <agriffis@gentoo.org> wrote:
> I think we might be best to try three revision control systems to
> start: darcs, git and subversion.  Three seems like a lot, but each
> has its reason, and we can anticipate darcs being used primarily by
> the haskell team rather than for overlays in general.

Many thanks for the summary.  I'll find some time to look at how we
can support darcs and git, and I'll post some news when I have some :)

Best regards,
Stu

-- 
gentoo-dev@gentoo.org mailing list



  reply	other threads:[~2006-03-31  8:21 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-24 19:35 [gentoo-dev] overlay support current proposal? Grant Goodyear
2006-03-24 19:54 ` Aron Griffis
2006-03-24 20:06 ` Daniel Ostrow
2006-03-24 20:13   ` Daniel Ostrow
2006-03-24 20:44   ` Stuart Herbert
2006-03-25  0:34     ` Alec Warner
2006-03-25  2:31     ` Diego 'Flameeyes' Pettenò
2006-03-25 11:41       ` Duncan Coutts
2006-03-25 11:49         ` Diego 'Flameeyes' Pettenò
2006-03-25 15:08           ` Carsten Lohrke
2006-03-25 18:50             ` Diego 'Flameeyes' Pettenò
2006-03-25 20:36               ` Carsten Lohrke
2006-03-25 22:17                 ` Stephen P. Becker
2006-03-25 11:42       ` Kevin F. Quinn (Gentoo)
2006-03-25 11:46         ` Duncan Coutts
2006-03-25 12:32           ` Kevin F. Quinn (Gentoo)
2006-03-25 12:37             ` Duncan Coutts
2006-03-25 13:28               ` Kevin F. Quinn (Gentoo)
2006-03-25 11:47         ` Diego 'Flameeyes' Pettenò
2006-03-25  6:47     ` Ryan Phillips
2006-03-25 11:55       ` [gentoo-dev] " Duncan
2006-03-25 23:00       ` [gentoo-dev] " Aron Griffis
2006-03-25 23:12         ` Aron Griffis
2006-03-25 23:20           ` Fernando J. Pereda
2006-03-25 23:18         ` Fernando J. Pereda
2006-03-26  0:57           ` Aron Griffis
2006-03-26  9:54             ` Fernando J. Pereda
2006-03-26 20:28             ` Greg KH
2006-03-27  5:43         ` Ryan Phillips
2006-03-27  8:29           ` Paul de Vrieze
2006-03-27 20:58             ` Dan Armak
2006-03-28  9:25               ` Paul de Vrieze
2006-03-27  8:51           ` Chris Bainbridge
2006-03-27 14:15             ` Chris Gianelloni
2006-03-26  1:30       ` Duncan Coutts
2006-03-26  4:39         ` Luca Barbato
2006-03-26  9:57           ` Fernando J. Pereda
2006-03-28 16:29             ` Patrick McLean
2006-03-30 12:40               ` Stuart Herbert
2006-03-30 18:54                 ` Aron Griffis
2006-03-31  8:16                   ` Stuart Herbert [this message]
2006-03-31  8:24                     ` Fernando J. Pereda
2006-03-31 11:36                       ` Duncan Coutts
2006-03-30 14:08               ` Nguyễn Thái Ngọc Duy
2006-03-25 10:16     ` Luca Barbato
2006-03-25 23:04       ` Aron Griffis
2006-03-25 23:32         ` 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=b38c6f4c0603310016m1cf9749dp7d5843860c70e4e3@mail.gmail.com \
    --to=stuart.herbert@gmail.com \
    --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