From: Brandon Casey <casey@nrlssc.navy.mil>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 2/2] filter-branch.sh: support nearly proper tag name filtering
Date: Mon, 24 Mar 2008 12:06:53 -0500 [thread overview]
Message-ID: <47E7DFAD.4060209@nrlssc.navy.mil> (raw)
In-Reply-To: <alpine.LSU.1.00.0803241745240.4353@racer.site>
Johannes Schindelin wrote:
> Hi,
>
> On Mon, 24 Mar 2008, Brandon Casey wrote:
>
>> So right now, tags matching the refspec are rewritten. They are currently
>> rewritten with a lightweight tag.
>
> That is unintended. My understanding of a tag was always that it is
> something immutable. I mean, _really_ immutable. If you released a
> certain version, then that is tagged. You must not rewrite the tag.
> Ever.
Then what is the intended behavior for --tag-name-filter?
-brandon
next prev parent reply other threads:[~2008-03-24 17:07 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
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 [this message]
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=47E7DFAD.4060209@nrlssc.navy.mil \
--to=casey@nrlssc.navy.mil \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).