public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Christian Faulhammer <fauli@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: New category for version control
Date: Thu, 4 Mar 2010 17:38:05 +0100	[thread overview]
Message-ID: <20100304173805.43b2ca2c@gentoo.org> (raw)
In-Reply-To: <4B8FDF1B.6030400@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 566 bytes --]

Hi,

Sebastian Pipping <sping@gentoo.org>:
> Agreed, "scm" is a bad choice.

 So it is really tracked in
http://bugs.gentoo.org/show_bug.cgi?id=56967 now.  If there is
anything to comment do it there.  Anyone can start moving the packages
over properly to dev-vcs (with profiles/updates entries of course), just
make it know somehow when you are working on packages not maintained by
you.

V-Li

-- 
Christian Faulhammer, Gentoo Lisp project
<URL:http://www.gentoo.org/proj/en/lisp/>, #gentoo-lisp on FreeNode

<URL:http://gentoo.faulhammer.org/>

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-03-04 16:38 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  9:07 [gentoo-dev] New category for version control Christian Faulhammer
2010-03-04  9:28 ` [gentoo-dev] " Dirkjan Ochtman
2010-03-04  9:32 ` [gentoo-dev] " Ulrich Mueller
2010-03-04  9:35   ` Ciaran McCreesh
2010-03-04 10:28     ` Petteri Räty
2010-03-04 10:37       ` Dirkjan Ochtman
2010-03-04 10:39         ` [gentoo-dev] " Christian Faulhammer
2010-03-04 15:14     ` [gentoo-dev] " Jeroen Roovers
2010-03-04 16:26     ` Sebastian Pipping
2010-03-04 16:38       ` Christian Faulhammer [this message]
2010-03-04 16:47         ` [gentoo-dev] " Sebastian Pipping
2010-03-04 19:20           ` Dirkjan Ochtman
2010-03-04 22:19           ` Christian Faulhammer
2010-03-05  0:27             ` Sebastian Pipping
2010-03-04  9:58   ` [gentoo-dev] " Alex Alexander
2010-03-04 12:54     ` Ben de Groot
2010-03-04 13:02   ` Antoni Grzymala

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=20100304173805.43b2ca2c@gentoo.org \
    --to=fauli@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