From: Junio C Hamano <junkio@cox.net>
To: barkalow@iabervon.org
Cc: git@vger.kernel.org
Subject: Re: Parallel pull for ssh-pull
Date: Tue, 02 Aug 2005 13:38:33 -0700 [thread overview]
Message-ID: <7vmzo09ira.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.62.0508021544430.23721@iabervon.org> (barkalow@iabervon.org's message of "Tue, 2 Aug 2005 16:02:59 -0400 (EDT)")
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.
prev parent reply other threads:[~2005-08-02 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-02 20:02 Parallel pull for ssh-pull barkalow
2005-08-02 20:38 ` Junio C Hamano [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7vmzo09ira.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).