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

Re: [PATCH] git-fetch: Split fetch and merge logic

From
Junio C Hamano <junkio@cox.net>
Date
Feb 24, 2007, 10:23 UTC
Message-ID
<7v8xenzwfg.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<87ps7zj35b.fsf@gmail.com>
Santi Béjar <sbejar@gmail.com> writes:
Show 6 quoted lines
>   I've addressed all the comments, now prepared to even more comments :)
>
>   Junio, from your "What's cooking in git.git (topics)" I undestand that
>   the jc/fetch topic is not going to be in next soon (even for the first
>   commit?). Anyway, the simple question is: Which branch (or commit) you
>   want me to base this patch?
For now this is fine.

I might have to postpone rebasing jc/fetch on top of this one depending on my workload, but I'd want this clean-up first.

Thanks.
Previous: Santi Béjar
Message 2 of 2 in “git-fetch: Split fetch and merge logic”
  1. git-fetch: Split fetch and merge logicSanti Béjar, Feb 24, 2007
  2. Junio C HamanoFeb 24, 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.