From: Junio C Hamano <gitster@pobox.com>
To: Mukund Sivaraman <muks@banu.com>
Cc: Jeff King <peff@peff.net>, git@vger.kernel.org
Subject: Re: Including branch info in git format-patch
Date: Thu, 19 Jun 2008 14:41:54 -0700 [thread overview]
Message-ID: <7vod5xrtjx.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20080619212626.GA29643@jurassic> (Mukund Sivaraman's message of "Fri, 20 Jun 2008 02:56:27 +0530")
Mukund Sivaraman <muks@banu.com> writes:
> My problem is that I can't send a patch out to the list for other
> developers to try, without some annotation for them, of which branch to
> try it on.
So what's wrong telling that when you send out the patch, between the time
you run format-patch and send-email?
next prev parent reply other threads:[~2008-06-19 21:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-19 15:42 Including branch info in git format-patch Mukund Sivaraman
2008-06-19 20:28 ` Jeff King
2008-06-19 20:54 ` Junio C Hamano
2008-06-19 21:06 ` Jeff King
2008-06-19 21:08 ` Jeff King
2008-06-19 21:15 ` Sverre Rabbelier
2008-06-19 21:26 ` Mukund Sivaraman
2008-06-19 21:41 ` Junio C Hamano [this message]
2008-06-19 21:55 ` Mukund Sivaraman
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=7vod5xrtjx.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=muks@banu.com \
--cc=peff@peff.net \
/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.