All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Ben Collins <bcollins@debian.org>
Cc: Pascal Schmidt <der.eremit@email.de>,
	Larry McVoy <lm@bitmover.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [BK-CVS gateway] version tags
Date: Wed, 11 Jun 2003 08:05:06 -0700	[thread overview]
Message-ID: <20030611150506.GB20493@work.bitmover.com> (raw)
In-Reply-To: <20030611135910.GO4695@phunnypharm.org>

On Wed, Jun 11, 2003 at 09:59:10AM -0400, Ben Collins wrote:
> On Wed, Jun 11, 2003 at 04:44:37PM +0200, Pascal Schmidt wrote:
> > 
> > Hi!
> > 
> > I noticed both the 2.4 and 2.5 BK->CVS trees don't have version tags
> > any more (v2_5_70, for example, as in the old tree).
> > 
> > Is this intentional? Did CVS take too long to tag all files or something?
> > 
> > It was quite a nice feature to have them, very useful for finding out the
> > differences between certain kernel versions. I can live without it, 
> > though. It's still a nice service without the tags. (Thanks!)
> 
> Looks like the tags are on the ChangeSet file only. Which is why I
> didn't notice. You could get a timestamp from the tag on ChangeSet and
> use that for a -D argument.
> 
> A quick script could do this for you. I think it's wise of Larry to keep
> it this way.

"Wise" is a stretch, more like a fortunate scripting screwup.  But I agree
with Ben, given that you can get the info another way it is a lot easier
(i.e., thrashes the disk less) if we leave it as is.
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-06-11 14:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-06-11 14:44 [BK-CVS gateway] version tags Pascal Schmidt
2003-06-11 13:59 ` Ben Collins
2003-06-11 15:05   ` Larry McVoy [this message]
2003-06-11 15:27     ` Pascal Schmidt
2003-06-11 14:47 ` Larry McVoy

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=20030611150506.GB20493@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=bcollins@debian.org \
    --cc=der.eremit@email.de \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.