git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: kill filter-branch --remap-to-ancestor?

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 25, 2010, 18:58 UTC
Message-ID
<7v39u2senj.fsf@alter.siamese.dyndns.org>
In-Reply-To
<i4pd55$19q$1@dough.gmane.org>
Csaba Henk <csaba@gluster.com> writes:
Show 13 quoted lines
> 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?

Previous: Csaba Henk
Message 2 of 2 in “kill filter-branch --remap-to-ancestor?”
  1. Csaba HenkAug 21, 2010
  2. Junio C HamanoAug 25, 2010

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.