git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Brandon Casey <casey@nrlssc.navy.mil>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] filter-branch.sh: support nearly proper tag name filtering
Date: Sun, 23 Mar 2008 22:49:45 -0700	[thread overview]
Message-ID: <7vr6e01xja.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LSU.1.00.0803201812560.4124@racer.site> (Johannes Schindelin's message of "Thu, 20 Mar 2008 18:14:45 +0100 (CET)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> On Thu, 20 Mar 2008, Brandon Casey wrote:
>
>> Add support for creating a new tag object and retaining the tag message, 
>> author, and date when rewriting tags. The gpg signature, if one exists, 
>> will be stripped.
>> 
>> This adds nearly proper tag name filtering to filter-branch. Proper tag 
>> name filtering would include the ability to change the tagger, tag date, 
>> tag message, and _not_ strip a gpg signature if the tag did not change.
>
> I think such a change in semantics merits a new option.

It is a different story if the fix is a good one, or has room for
improvement.  For example, the sed script that knows what is on the first
and second line and relies on that knowledge to use 1c...2c... looked very
fragile to me.

However, at least to me, this looked like an attempt for a pure "fix".

If you tell filter-branch to filter a branch A and a tag T, as the command
is advertised to rewrite positive refs that were given from the command
line, isn't it natural to expect that the command would attempt its best
effort to rewrite such a tag object?

  parent reply	other threads:[~2008-03-24  5:50 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1206031893-29599-1-git-send-email-casey@nrlssc.navy.mil>
2008-03-20 17:02 ` [PATCH 2/2] filter-branch.sh: support nearly proper tag name filtering Brandon Casey
2008-03-20 17:14   ` Johannes Schindelin
2008-03-20 17:38     ` Brandon Casey
2008-03-24  5:49     ` Junio C Hamano [this message]
2008-03-24 10:53       ` Johannes Schindelin
2008-03-24 14:49         ` Junio C Hamano
2008-03-24 15:10           ` Johannes Schindelin
2008-03-24 16:34             ` Brandon Casey
2008-03-24 16:45               ` Brandon Casey
2008-03-24 16:46               ` Johannes Schindelin
2008-03-24 17:06                 ` Brandon Casey
2008-03-24 17:14                   ` Johannes Schindelin
2008-03-24 18:37                     ` Brandon Casey
2008-03-24 21:22             ` filter-branch --all? Eyvind Bernhardsen
2008-03-24 21:33               ` Brandon Casey
2008-03-24 21:44                 ` Eyvind Bernhardsen
2008-03-24 19:02       ` [PATCH 2/2] filter-branch.sh: support nearly proper tag name filtering Brandon Casey
2008-03-24 22:09         ` [PATCH] " Brandon Casey
2008-03-24 22:14           ` Brandon Casey
2008-03-25  1:14           ` Junio C Hamano
2008-03-25 15:44             ` [PATCH v3] " Brandon Casey
2008-03-26  7:57               ` Junio C Hamano
2008-03-26 15:47                 ` [PATCH v4] " Brandon Casey

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=7vr6e01xja.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=casey@nrlssc.navy.mil \
    --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).