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

Re: [PATCH 2/2] add [--] to usage of filter-branch

From
Junio C Hamano <gitster@pobox.com>
Date
Jun 9, 2017, 13:14 UTC
Message-ID
<xmqqk24l717a.fsf@gitster.mtv.corp.google.com>
In-Reply-To
<ef30e8f5-8206-7b42-e229-6cd4b0492e76@gmail.com>
Andreas Heiduk <asheiduk@gmail.com> writes:
Show 20 quoted lines
> Am 03.06.2017 um 12:17 schrieb Andreas Heiduk:
>> Signed-off-by: Andreas Heiduk <asheiduk@gmail.com>
>> ---
>>  Documentation/git-filter-branch.txt | 3 ++-
>>  git-filter-branch.sh                | 2 +-
>>  2 files changed, 3 insertions(+), 2 deletions(-)
>> 
>> diff --git a/Documentation/git-filter-branch.txt b/Documentation/git-filter-branch.txt
>> index 45c849d8c..1efdda804 100644
>> --- a/Documentation/git-filter-branch.txt
>> +++ b/Documentation/git-filter-branch.txt
>> @@ -86,7 +86,8 @@ OPTIONS
>>  	This is not a real filter executed for each commit but a one
>>  	time setup just before the loop. Therefore no commit-specific
>>  	variables are defined yet.  Functions or variables defined here
>> -	can be used or modified in the following filter steps.
>> +	can be used or modified in the following filter steps except
>> +	the commit filter, for technical reasons.
>
> I'll move that into the previous commit.

Yeah, the description of "technical limitation" is different from clarifying the disambiguating "--" in the documentation.

I am curious what the "technical reason" really is, though ;-)
Previous: Andreas HeidukNext: Andreas Heiduk
Message 4 of 10 in “add setup step to filter-branch”
  1. 1/2 add setup step to filter-branchAndreas Heiduk, Jun 3, 2017
  2. 2/2 add [--] to usage of filter-branchAndreas Heiduk, Jun 3, 2017
  3. Andreas HeidukJun 5, 2017
  4. Junio C HamanoJun 9, 2017
  5. Andreas HeidukJun 9, 2017
  6. Junio C HamanoJun 5, 2017
  7. Jeff KingJun 9, 2017
  8. Junio C HamanoJun 9, 2017
  9. 1/2 add setup step to filter-branchAndreas Heiduk, Jun 10, 2017
  10. 2/2 add [--] to usage of filter-branchAndreas Heiduk, Jun 10, 2017

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.