{"thread":{"id":"24822","subject":"kill filter-branch --remap-to-ancestor?","startedAt":"2010-08-21T20:32:37Z","lastAt":"2010-08-25T18:58:24Z","messageCount":2,"participants":["Csaba Henk","Junio C Hamano"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"148688","messageId":"i4pd55$19q$1@dough.gmane.org","threadId":"24822","inReplyTo":null,"subject":"kill filter-branch --remap-to-ancestor?","fromName":"Csaba Henk","fromEmail":"csaba@gluster.com","sentAt":"2010-08-21T20:32:37Z","receivedAt":"2010-08-21T20:32:37Z","isPatch":false,"sender":{"key":"csaba@gluster.com","avatar":"https://avatars.githubusercontent.com/u/43937?v=4"},"body":"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). \n\nThis time, in a similar situation, I had some headache with finding out that the panacea is already there and it's called \"--rema\np-to-ancestor\".\n\nWhy 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\nhttp://thread.gmane.org/gmane.comp.version-control.git/130949/focus=132684).\n\nCsaba\n"},{"id":"148986","messageId":"7v39u2senj.fsf@alter.siamese.dyndns.org","threadId":"24822","inReplyTo":"i4pd55$19q$1@dough.gmane.org","subject":"Re: kill filter-branch --remap-to-ancestor?","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2010-08-25T18:58:24Z","receivedAt":"2010-08-25T18:58:24Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Csaba Henk <csaba@gluster.com> writes:\n\n> I had some headache with the issue to which the cure is the\n> \"--remap-to-ancestor\" option of git filter-branch -- back when\n> \"--remap-to-ancestor\" was not yet\n> (cf. http://thread.gmane.org/gmane.comp.version-control.git/112068/focus=112838).\n>\n> This time, in a similar situation, I had some headache with finding out\n> that the panacea is already there and it's called \"--remap-to-ancestor\".\n>\n> Why not cut back on complexity and get rid of \"--remap-to-ancestor\"\n> while automatically enable the implied behavior for filters including a\n> path? This was already proposed by Junio and the author of the option\n> had no objections against this idea (see\n> http://thread.gmane.org/gmane.comp.version-control.git/130949/focus=132684).\n\nI am not a heavy user of filter-branch myself (I used it once during the\npast 6 months and it was with pathspec but the project did not have any\ntags, so that particular exercise does not matter).\n\nI do not offhand see a reason not to.  Please make it so, if you are\nso inclined, or perhaps somebody else may volunteer?\n"}]}