public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Fabian Groffen <grobian@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Usages of CVS $Header$ keyword in ebuilds - use cases wanted
Date: Wed, 27 Aug 2008 21:24:34 +0200	[thread overview]
Message-ID: <20080827192434.GL27338@gentoo.org> (raw)
In-Reply-To: <20080827191535.GM30560@curie-int.orbis-terrarum.net>

On 27-08-2008 12:15:35 -0700, Robin H. Johnson wrote:
> For those not using SSH ControlMaster, one of the side-effects of having
> to do two separate commits is the SSH setup latency hitting twice.
> 
> I wouldn't call it repoman's fault like Fabian did, but the

Right.  I thought I suggested that "it" (the double-commit) is a mess
for repoman.  Not that it is repoman's fault.

> double-commit is why I called it a mess. If we drop the $Header$ in any
> file covered by a developer-generated Manifest, it becomes a single
> commit with contents+Manifest :-).

It seems that what you call "mess" means needing a double commit for a
single "repoman commit".  That to me isn't a mess, but a performance
issue, and as I indicated a possible point of corruption.  But we've
dealt long enough with the situation without problems to ignore that
point.

But to repeat:
- no I'm not against removing the $Header: $ stuff
- yes I'd even like to use another VCS which can make my life easer
- but, as long as we're on CVS, I'd prefer it when you'd keep my life
  sort of bearable
- so, keep the $Header: $ stuff for Prefix' sake (me) as long as
  we're using CVS


-- 
Fabian Groffen
Gentoo on a different level



  reply	other threads:[~2008-08-27 19:24 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-26 20:40 [gentoo-dev] Usages of CVS $Header$ keyword in ebuilds - use cases wanted Robin H. Johnson
2008-08-26 20:41 ` Yuri Vasilevski
2008-08-26 20:54   ` Robin H. Johnson
2008-08-26 20:59     ` Yuri Vasilevski
2008-08-26 21:45       ` Robin H. Johnson
2008-08-26 21:57         ` Yuri Vasilevski
2008-08-26 22:25           ` Robin H. Johnson
2008-08-26 22:37             ` René 'Necoro' Neumann
2008-08-26 22:54               ` Robin H. Johnson
2008-08-26 23:19                 ` René 'Necoro' Neumann
2008-08-26 23:28                   ` René 'Necoro' Neumann
2008-08-26 22:46             ` Yuri Vasilevski
2008-08-26 22:46         ` Raúl Porcel
2008-08-27 16:35   ` Fabian Groffen
2008-08-27 17:28     ` Robin H. Johnson
2008-08-27 17:38       ` Fabian Groffen
2008-08-27 18:57         ` Alec Warner
2008-08-27 19:15           ` Robin H. Johnson
2008-08-27 19:24             ` Fabian Groffen [this message]
2008-08-27 19:16           ` Fabian Groffen
2008-08-26 20:46 ` Mart Raudsepp
2008-08-27 17:12 ` Paul Varner
2008-10-01 15:31 ` Thilo Bangert
2008-10-01 23:21   ` Robin H. Johnson

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=20080827192434.GL27338@gentoo.org \
    --to=grobian@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