git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: "Stephen R. van den Berg" <srb@cuci.nl>
Cc: git@vger.kernel.org
Subject: Re: [updated PATCH] Protect current tags, import tags into remote tree
Date: Mon, 28 Apr 2008 23:18:33 -0700	[thread overview]
Message-ID: <7vbq3t89qe.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080428184859.GA21950@cuci.nl> (Stephen R. van den Berg's message of "Mon, 28 Apr 2008 20:48:59 +0200")

"Stephen R. van den Berg" <srb@cuci.nl> writes:

> Rerunning cvsimport on a regular basis causes the import to (re)create
> all the tags from CVS again; if this is done in your regular tags space,
> this is a mess at best, or overwrites whatever renamed tags you
> carefully created which happen to match with old CVS tagnames.
> ...
> - git-svn and git-cvsimport cross the boundary to a different VCS and
>   therefore can/should use an extra barrier before (auto)converting to
>   git native tags (and branches).

That sounds like a sound argument, and perhaps people may wish we did so
from the day one.  Alas, we didn't.

So the course of action would be to do these over a long period of time.

 - introduce this as an option now;

 - give another option to explicitly ask for the current behaviour;

 - perhaps give an advance warning that this optional behaviour will
   become the default; and

 - finally swap the default behaviour.

if people agree with this change, that is.

      reply	other threads:[~2008-04-29  6:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-27 17:32 [updated PATCH] Protect current tags, import tags into remote tree Stephen R. van den Berg
2008-04-28 16:12 ` Junio C Hamano
2008-04-28 18:48   ` Stephen R. van den Berg
2008-04-29  6:18     ` Junio C Hamano [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=7vbq3t89qe.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=srb@cuci.nl \
    /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).