From: Junio C Hamano <gitster@pobox.com>
To: Csaba Henk <csaba@gluster.com>
Cc: git@vger.kernel.org
Subject: Re: kill filter-branch --remap-to-ancestor?
Date: Wed, 25 Aug 2010 11:58:24 -0700 [thread overview]
Message-ID: <7v39u2senj.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <i4pd55$19q$1@dough.gmane.org> (Csaba Henk's message of "Sat\, 21 Aug 2010 20\:32\:37 +0000 \(UTC\)")
Csaba Henk <csaba@gluster.com> writes:
> I had some headache with the issue to which the cure is the
> "--remap-to-ancestor" option of git filter-branch -- back when
> "--remap-to-ancestor" was not yet
> (cf. http://thread.gmane.org/gmane.comp.version-control.git/112068/focus=112838).
>
> This time, in a similar situation, I had some headache with finding out
> that the panacea is already there and it's called "--remap-to-ancestor".
>
> Why not cut back on complexity and get rid of "--remap-to-ancestor"
> while automatically enable the implied behavior for filters including a
> path? This was already proposed by Junio and the author of the option
> had no objections against this idea (see
> http://thread.gmane.org/gmane.comp.version-control.git/130949/focus=132684).
I am not a heavy user of filter-branch myself (I used it once during the
past 6 months and it was with pathspec but the project did not have any
tags, so that particular exercise does not matter).
I do not offhand see a reason not to. Please make it so, if you are
so inclined, or perhaps somebody else may volunteer?
prev parent reply other threads:[~2010-08-25 18:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-21 20:32 kill filter-branch --remap-to-ancestor? Csaba Henk
2010-08-25 18:58 ` 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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7v39u2senj.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=csaba@gluster.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).