git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jonathan Nieder <jrnieder@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: Thu, 8 Apr 2010 10:24:34 +0530	[thread overview]
Message-ID: <x2of3271551004072154r62d10023r32e74064d38aff75@mail.gmail.com> (raw)
In-Reply-To: <7vzl1eamss.fsf@alter.siamese.dyndns.org>

Hi,

On Thu, Apr 8, 2010 at 4:19 AM, Jonathan Nieder <jrnieder@gmail.com> wrote:
> Thank you for this.  FWIW I find it useful when discussing a piece of
> code or documentation to bounce back and forth multiple versions of
> small fragments.  Then once the discussion has settled down, it can be
> useful to see the big picture again, with the new changes
> incorporated.

Got it. In future, I'll post diffs for smaller changes hopefully in
the same email thread, and complete patches for larger changes in a
separate email thread. I've been quite haphazard in the past.

> 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.

Ah, I already do that, but my branch is based on `pu`. What should I do?
http://github.com/artagnon/git

On Thu, Apr 8, 2010 at 4:32 AM, Junio C Hamano <gitster@pobox.com> wrote:
> At least it would be helpful for me if people based their follow-up
> patches on top of their own topics.

Can I see the topic branch corresponding to my patches? If this is
possible, I can avoid the more painful procedure of extracting it from
the latest pu using git-resurrect.sh.

-- Ram

  reply	other threads:[~2010-04-08  4:55 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
2010-04-08  4:54         ` Ramkumar Ramachandra [this message]
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=x2of3271551004072154r62d10023r32e74064d38aff75@mail.gmail.com \
    --to=artagnon@gmail.com \
    --cc=barkalow@iabervon.org \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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 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).