public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Daniel Drake <dsd@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] GLEP 36: providing both CVS and Subversion?
Date: Sun, 10 Apr 2005 22:30:29 +0100	[thread overview]
Message-ID: <42599AF5.6050103@gentoo.org> (raw)
In-Reply-To: <1113156876.30765.5.camel@pursuit>

Lance Albertson wrote:
> Before everyone starts getting all antsy about getting svn for gentoo
> projects, its in the works. I'm trying to get the current CVS admins
> around so we can start with that process. Robbat2 seems to be busy for
> the next few weeks, so I'll have to rely on Pylon to help with this. So
> please just be patient and we'll get this rolling soon. Bugging me or
> other people about will not get you anywhere :P

I doubt this is the right place to ask, but I got no reply from the trustees,
so...

A while back, we had to move the gentoo kernel patches out of the Gentoo CVS
because we realised it conflicted with the old copyright assignment form: I
have signed an agreement saying that everything I put in gentoo cvs will be
copyrighted to Gentoo. That obviously isn't the case for kernel patches that I
didn't write.

We moved the kernel patches into a bitkeeper repo, and they've been there for
a while. However, this might be clashing with the social contract, and
costless BK is going away, so its time to move again. I'd love to host these
in a Gentoo repo, preferably SVN, but would need to get that agreement revoked
for me and the other kernel developers. Who do I need to speak to?

Thanks,
Daniel
--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2005-04-10 21:26 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-10 16:39 [gentoo-dev] GLEP 36: providing both CVS and Subversion? Aaron Walker
2005-04-10 17:12 ` Ciaran McCreesh
2005-04-10 17:27   ` Patrick Lauer
2005-04-10 17:32     ` Ciaran McCreesh
2005-04-10 17:47       ` Christian Parpart
2005-04-10 17:44     ` Christian Parpart
2005-04-10 17:53       ` Ciaran McCreesh
2005-04-10 18:27         ` Christian Parpart
2005-04-10 18:34           ` Ciaran McCreesh
2005-04-10 21:57             ` Christian Parpart
2005-04-11  6:26               ` Ciaran McCreesh
2005-04-11 20:23                 ` Christian Parpart
2005-04-11 20:42                   ` Ciaran McCreesh
2005-04-11 21:32                     ` Christian Parpart
2005-04-12 18:50                     ` Paul de Vrieze
2005-04-12 18:57                       ` Ciaran McCreesh
2005-04-13  1:33                         ` Christian Parpart
2005-04-13  6:26                           ` Ciaran McCreesh
2005-04-13 13:03                             ` Aaron Walker
2005-04-13 14:46                               ` Christian Parpart
2005-04-10 18:14 ` Lance Albertson
2005-04-10 18:23   ` Ciaran McCreesh
2005-04-10 21:30   ` Daniel Drake [this message]
2005-04-10 21:35     ` Greg KH
2005-04-10 21:44       ` Christian Parpart
2005-04-10 22:08         ` Daniel Drake
2005-04-10 21:48       ` Patrick Lauer
2005-04-10 22:00         ` Lance Albertson
2005-04-10 22:20       ` Donnie Berkholz
2005-04-12 23:22     ` Nicholas Jones
2005-04-12 18:31 ` Paul de Vrieze

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=42599AF5.6050103@gentoo.org \
    --to=dsd@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