All of lore.kernel.org
 help / color / mirror / Atom feed
From: Martin Langhoff <martin.langhoff@gmail.com>
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: Git Mailing List <git@vger.kernel.org>, Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] git-cvsimport-script: handling of tags
Date: Wed, 7 Sep 2005 09:21:24 +1200	[thread overview]
Message-ID: <46a038f905090614216eca87eb@mail.gmail.com> (raw)
In-Reply-To: <431DFB04.5020701@zytor.com>

On 9/7/05, H. Peter Anvin <hpa@zytor.com> wrote:
> > I should probably point out that there are still bugs in
> > git-cvsimport-script; for one thing, it seems to fail to register a tag
> > associated with the head, and I have yet to get the "recognize merge"
> > feature to actually work.  It's also possible -- but I haven't verified
> > it -- that two tags which are aliases may not be properly registered.
> I just verified this; git-cvsimport-script will not handle more than one
> tag per commit.

Tell me more about how you are trying the 'recognize merge'. It is a
pretty unsophisticated thing, as it trusts the commit message in the
first place. But when it works, it works.

I have a more refined merge detection already working in the Arch
imports -- patch coming soon -- but with cvs it is pretty hard to do.

cheers,


martin

  reply	other threads:[~2005-09-06 21:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-09-06 17:36 [PATCH] git-cvsimport-script: handling of tags H. Peter Anvin
2005-09-06 18:56 ` H. Peter Anvin
2005-09-06 20:24   ` H. Peter Anvin
2005-09-06 21:21     ` Martin Langhoff [this message]
2005-09-06 21:33       ` H. Peter Anvin
2005-09-06 22:59         ` Martin Langhoff
2005-09-06 23:19           ` H. Peter Anvin
2005-09-06 19:01 ` Junio C Hamano
2005-09-07  2:44 ` Martin Langhoff
2005-09-07  2:48   ` H. Peter Anvin

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=46a038f905090614216eca87eb@mail.gmail.com \
    --to=martin.langhoff@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=hpa@zytor.com \
    --cc=junkio@cox.net \
    /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.