From: Martin Langhoff <martin.langhoff@gmail.com>
To: Dave Jones <davej@redhat.com>
Cc: git@vger.kernel.org
Subject: Re: FUNKY tags.
Date: Wed, 17 Aug 2005 12:55:18 +1200 [thread overview]
Message-ID: <46a038f90508161755b43735c@mail.gmail.com> (raw)
In-Reply-To: <20050816224332.GE26455@redhat.com>
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.
I am somewhat worried about cvsps getting confused by these floating
tags. Any help in teaching cvsps to ignore tags is welcome ;)
m
next prev parent reply other threads:[~2005-08-17 0:56 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 [this message]
2005-08-17 2:47 ` Dave Jones
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=46a038f90508161755b43735c@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=davej@redhat.com \
--cc=git@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;
as well as URLs for NNTP newsgroup(s).