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

Re: Parallel pull for ssh-pull

From
Junio C Hamano <junkio@cox.net>
Date
Aug 2, 2005, 20:38 UTC
Message-ID
<7vmzo09ira.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.62.0508021544430.23721@iabervon.org>
barkalow@iabervon.org writes:
> This work is based on some now in -pu; what should I base my patches on? I 
> would ideally like to add a function to one of the patches in -pu and fix 
> a subtle bug in the other, in addition to further patches to actually use 
> the feature in ssh-pull.

The proposed patch queue is just a throw-away branch that I use for the purpose of (1) not to lose patches from people, (2) to ack patches from others, and (3) let people know which ones are under consideration.

Either a patch on top of the pu branch, or a brand new patch on top of the master branch would work fine for me. If you feel some stuff that are in pu need to be fixed or cleaned up, you may want choose the latter --- that way, software archaeologists do not need to know that you made a mess in earlier rounds ;-). If you choose to do so, I would appreciate a warning to tell me which existing patches to drop from pu, although that would probably be pretty clear from the context.

Thanks.
Previous: barkalow@iabervon.org
Message 2 of 2 in “Parallel pull for ssh-pull”
  1. barkalow@iabervon.orgAug 2, 2005
  2. Junio C HamanoAug 2, 2005

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.