From: Junio C Hamano <gitster@pobox.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
Ilari Liusvaara <ilari.liusvaara@elisanet.fi>,
Daniel Barkalow <barkalow@iabervon.org>,
Gabriel Filion <lelutin@gmail.com>,
Sverre Rabbelier <srabbelier@gmail.com>,
Michael J Gruber <git@drmicha.warpmail.net>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH v9] Documentation/remote-helpers: Add invocation section
Date: Wed, 07 Apr 2010 16:02:43 -0700 [thread overview]
Message-ID: <7vzl1eamss.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20100407224942.GA20239@progeny.tock> (Jonathan Nieder's message of "Wed\, 7 Apr 2010 17\:49\:43 -0500")
Jonathan Nieder <jrnieder@gmail.com> writes:
> If you want to make sure the latest version of a patch is always
> available, that is a noble goal, too, but I think a frequently-
> rebased public branch for your patch series is a better way to achieve
> that.
>
> Unrelated: in case you are interested, the git-resurrect.sh script
> from contrib can extract topic branches from pu, if you want to see
> Junio’s topic branch for your patch.
It might look unrelated, but I found it the most helpful information in
your message ;-) I really hate it when people base their patches on 'pu'.
At least it would be helpful for me if people based their follow-up
patches on top of their own topics.
next prev parent reply other threads:[~2010-04-07 23:03 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 5:57 [PATCH v9] Documentation/remote-helpers: Add invocation section Ramkumar Ramachandra
2010-04-07 8:56 ` Ramkumar Ramachandra
2010-04-07 15:05 ` Junio C Hamano
2010-04-07 16:50 ` Ramkumar Ramachandra
2010-04-07 17:23 ` Junio C Hamano
2010-04-07 17:58 ` Ramkumar Ramachandra
2010-04-07 22:49 ` Jonathan Nieder
2010-04-07 23:02 ` Junio C Hamano [this message]
2010-04-08 4:54 ` Ramkumar Ramachandra
2010-04-08 5:03 ` Jonathan Nieder
2010-04-08 5:14 ` Junio C Hamano
2010-04-10 12:24 ` Ramkumar Ramachandra
2010-04-08 18:52 ` Sverre Rabbelier
2010-04-08 20:01 ` Re*: " Junio C Hamano
2010-04-08 20:21 ` Sverre Rabbelier
2010-04-08 20:45 ` Junio C Hamano
2010-04-09 2:06 ` Michael J Gruber
2010-04-10 4:59 ` Junio C Hamano
2010-04-10 12:36 ` Ramkumar Ramachandra
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=7vzl1eamss.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=artagnon@gmail.com \
--cc=barkalow@iabervon.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=ilari.liusvaara@elisanet.fi \
--cc=jrnieder@gmail.com \
--cc=lelutin@gmail.com \
--cc=srabbelier@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.