From: Larry McVoy <lm@bitmover.com>
To: Pascal Schmidt <der.eremit@email.de>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: [BK-CVS gateway] version tags
Date: Wed, 11 Jun 2003 07:47:31 -0700 [thread overview]
Message-ID: <20030611144731.GA20493@work.bitmover.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0306111641140.1602-100000@neptune.local>
I'll go look. CVS takes way too long to tag, it forces a rewrite of
every file. I did attempt to filter out tags that weren't of the forn
v2.* but it looks like I screwed up.
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!)
>
> --
> Ciao,
> Pascal
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
prev parent reply other threads:[~2003-06-11 14:33 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
2003-06-11 15:27 ` Pascal Schmidt
2003-06-11 14:47 ` Larry McVoy [this message]
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=20030611144731.GA20493@work.bitmover.com \
--to=lm@bitmover.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox