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

Re: What's cooking in git.git (Jan 2010, #05; Sat, 16)

From
Avery Pennarun <apenwarr@gmail.com>
Date
Jan 28, 2010, 21:16 UTC
Message-ID
<32541b131001281316m59128e7ds45353a30ac602b6f@mail.gmail.com>
In-Reply-To
<7vd417udpi.fsf@alter.siamese.dyndns.org>
On Mon, Jan 18, 2010 at 1:30 AM, Junio C Hamano <gitster@pobox.com> wrote:
Show 19 quoted lines
> Junio C Hamano <gitster@pobox.com> writes:
>
>> [Stalled]
>>
>> * ap/merge-backend-opts (2008-07-18) 6 commits
>>  - Document that merge strategies can now take their own options
>>  - Extend merge-subtree tests to test -Xsubtree=dir.
>>  - Make "subtree" part more orthogonal to the rest of merge-recursive.
>>  - Teach git-pull to pass -X<option> to git-merge
>>  - git merge -X<option>
>>  - git-merge-file --ours, --theirs
>>
>> "git pull" patch needs sq-then-eval fix to protect it from $IFS
>> but otherwise seemed good.
>
> Generally I hate to step in to fix up other's series, especially when I
> know that the party responsible for issues is capable enough.  As the
> pre-release feature freeze gets closer, however, I sometimes find myself
> doing so, and (I repeat) I hate it.
Sorry about that.  I asked at the time whether you thought I should
submit a patch or whether you were planning to do it, and didn't get
an answer.  And then when you wrote the above, I was away on vacation.
 I see it's now been merged into master, but in case you care... it
looks ok to me :)
Have fun,
Avery
Previous: Junio C Hamano
Message 5 of 5 in “What's cooking in git.git (Jan 2010, #05; Sat, 16)”
  1. Junio C HamanoJan 17, 2010
  2. Jeff KingJan 17, 2010
  3. Jakub NarebskiJan 18, 2010
  4. Junio C HamanoJan 18, 2010
  5. Avery PennarunJan 28, 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.