From: Dave Jones <davej@redhat.com>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: FUNKY tags.
Date: Tue, 16 Aug 2005 22:47:18 -0400 [thread overview]
Message-ID: <20050817024718.GA11734@redhat.com> (raw)
In-Reply-To: <46a038f90508161755b43735c@mail.gmail.com>
On Wed, Aug 17, 2005 at 12:55:18PM +1200, Martin Langhoff wrote:
> On 8/17/05, Dave Jones <davej@redhat.com> wrote:
> > I've no idea what I did when I tagged those trees, but according
> > to a google search, cvsps does that when it find patchsets which
> > are chronologically (and thus by patchset id) earlier than the tag,
> > but are tagwise after. Spooky.
>
> It's probably tags that were moved around with "cvs tag -F footag".
> When using cvs in with a dovetail strategy, people tend to merge
> BRANCH->HEAD and use a floating tag to mark how far it's been merged
> in.
In my case, at least the most recent of those cvs tag operations
was just a 'cvs tag x86info-1_14'. Nothing fancy. I'm fairly sure
there was nothing fancy about the earlier instance either.
So sure in fact, I had to look up that -F flag in the man page to find
out what it did.
x86info cvs shouldn't even have any branches, so theres no strange
head merging going on.
> I am somewhat worried about cvsps getting confused by these floating
> tags. Any help in teaching cvsps to ignore tags is welcome ;)
If you're curious, its a sourceforge project at cvs.sourceforge.net:/cvsroot/x86info
module is 'x86info'. Both x86info-1_14 and x86info-1_6 are marked as funky
for reasons I'm unaware.
Dave
next prev parent reply other threads:[~2005-08-17 2:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-16 22:43 FUNKY tags Dave Jones
2005-08-17 0:55 ` Martin Langhoff
2005-08-17 2:47 ` Dave Jones [this message]
2005-08-17 5:59 ` Martin Langhoff
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=20050817024718.GA11734@redhat.com \
--to=davej@redhat.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).