public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Eray Aslan <eras@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] git? [was: Re: Devmanual text on ChangeLogs]
Date: Sun, 1 May 2011 13:09:15 +0300	[thread overview]
Message-ID: <20110501100915.GB10191@zptr-nb18> (raw)
In-Reply-To: <4DBD22A7.3080500@gentoo.org>

On Sun, May 01, 2011 at 12:06:47PM +0300, Samuli Suominen wrote:
> ... the time alone if you have to stop on each package to wait for
> echangelog to get done just doubles the amount of time you have to put
> into committing them. That's just not worth the effort.

Won't moving the tree to git will make this a moot discussion?  These and
similar solutions look more and more lika a band-aid to the defecencies
of cvs.

What is it really that is holding us up?  A dev to spearhead the move?

-- 
Eray Aslan
Developer, Gentoo Linux       eras <at> gentoo.org



  reply	other threads:[~2011-05-01 10:10 UTC|newest]

Thread overview: 50+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-30  8:46 [gentoo-dev] Devmanual text on ChangeLogs Petteri Räty
2011-04-30  9:02 ` Samuli Suominen
2011-04-30 12:12   ` Peter Volkov
2011-05-02  2:23     ` Jeroen Roovers
2011-04-30 13:42   ` Markos Chandras
2011-04-30 14:24     ` Brian Harring
2011-04-30 18:16     ` Alex Alexander
2011-04-30 20:39   ` Panagiotis Christopoulos
2011-05-01  9:06     ` Samuli Suominen
2011-05-01 10:09       ` Eray Aslan [this message]
2011-05-01 10:54         ` [gentoo-dev] git? Panagiotis Christopoulos
2011-05-01 11:25           ` Andreas K. Huettel
2011-05-01 18:05         ` [gentoo-dev] git? [was: Re: Devmanual text on ChangeLogs] Maciej Mrozowski
2011-05-01 10:34       ` [gentoo-dev] Devmanual text on ChangeLogs Fabian Groffen
2011-05-01 10:44       ` Panagiotis Christopoulos
2011-05-01 11:26         ` Peter Volkov
2011-05-01 11:26       ` Andreas K. Huettel
2011-05-01 20:43       ` Brian Harring
2011-05-02  2:43         ` Jeroen Roovers
2011-04-30  9:07 ` Ulrich Mueller
2011-04-30 11:21   ` Panagiotis Christopoulos
2011-05-02  2:52     ` Jeroen Roovers
2011-04-30 12:28   ` [gentoo-dev] " Diego Elio Pettenò
2011-04-30 13:05     ` Panagiotis Christopoulos
2011-04-30 13:44       ` "Paweł Hajdan, Jr."
2011-04-30 14:00         ` Rich Freeman
2011-04-30  9:57 ` [gentoo-dev] " Pacho Ramos
2011-05-01 10:00 ` Fabian Groffen
2011-05-01 14:55   ` [gentoo-dev] " Duncan
2011-05-01 15:08     ` Fabian Groffen
2011-05-01 21:08   ` [gentoo-dev] " Markos Chandras
2011-05-01 22:33     ` Brian Harring
2011-05-01 22:49       ` Markos Chandras
2011-05-01 23:23         ` [gentoo-dev] " Duncan
2011-05-01 23:31           ` Brian Harring
2011-05-01 23:43             ` Rich Freeman
2011-05-02  0:13               ` Markos Chandras
2011-05-02  1:15               ` Duncan
2011-05-02  6:48               ` Fabian Groffen
2011-05-02  0:16             ` Markos Chandras
2011-05-02 21:10               ` Arfrever Frehtes Taifersar Arahesis
2011-05-01 23:11     ` Duncan
2011-05-02  0:04     ` [gentoo-dev] " Ulrich Mueller
2011-05-02  0:21       ` Markos Chandras
2011-05-02  1:20       ` Nirbheek Chauhan
2011-05-02  1:24         ` Robin H. Johnson
2011-05-02  1:37           ` Nirbheek Chauhan
2011-05-02  5:17         ` Ulrich Mueller
2011-05-02  6:51       ` Fabian Groffen
2011-05-02 21:24 ` Gilles Dartiguelongue

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=20110501100915.GB10191@zptr-nb18 \
    --to=eras@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