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

Re: [PATCH] config.txt: update branch.<name>.merge documentation

From
Junio C Hamano <junkio@cox.net>
Date
Feb 4, 2007, 00:38 UTC
Message-ID
<7v4pq221vd.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<8aa486160702031630l4fd3e29did4f249713cf2ce81@mail.gmail.com>
"Santi Béjar" <sbejar@gmail.com> writes:
Show 13 quoted lines
> On 2/3/07, Santi Béjar <sbejar@gmail.com> wrote:
>> --- a/Documentation/config.txt
>> +++ b/Documentation/config.txt
>> @@ -233,11 +233,12 @@ branch.<name>.remote::
>>  branch.<name>.merge::
>>         When in branch <name>, it tells `git fetch` the default refspec to
>>         be marked for merging in FETCH_HEAD. The value has exactly to match
>> -       a remote part of one of the refspecs which are fetched from the remote
>> -       given by "branch.<name>.remote".
>> +       the remote or local part of one of the refspecs which are fetched
>> +       from the remote given by "branch.<name>.remote".
>
> It is OK, but ...

Yeah, but I am starting to think that it was a mistake to allow an additional way to express the same thing.

Reverting 80c797764 would make the implementation to match the specification described in the original.

Previous: Santi Béjar
Message 6 of 6 in “config.txt: update branch.<name>.merge documentation”
  1. config.txt: update branch.<name>.merge documentationSanti Béjar, Feb 3, 2007
  2. Yann DirsonFeb 3, 2007
  3. Santi BéjarFeb 3, 2007
  4. Yann DirsonFeb 3, 2007
  5. Santi BéjarFeb 4, 2007
  6. Junio C HamanoFeb 4, 2007

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.