From: Johannes Schindelin <johannes.schindelin@gmx.de>
To: Lars Wendler <polynomial-c@gentoo.org>
Cc: git@vger.kernel.org, juston.h.li@gmail.com,
Stefan Agner <stefan@agner.ch>
Subject: Re: [PATCH] git-send-email.perl: Fixed sending of many changes/patches
Date: Tue, 29 Sep 2015 17:43:25 +0200 [thread overview]
Message-ID: <e6d296ecf9f32f74c709714ca0de14ba@dscho.org> (raw)
In-Reply-To: <1443538820-20023-1-git-send-email-polynomial-c@gentoo.org>
Hi Lars,
On 2015-09-29 17:00, Lars Wendler wrote:
> From: Stefan Agner <stefan@agner.ch>
>
> See http://permalink.gmane.org/gmane.comp.version-control.git/274569
Please summarize the linked discussion in the commit message, as it is the convention here in the Git project to make commit messages self-sufficient, with links thrown in only to provide more context when desired.
Ciao,
Johannes
prev parent reply other threads:[~2015-09-29 15:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-29 15:00 [PATCH] git-send-email.perl: Fixed sending of many changes/patches Lars Wendler
2015-09-29 15:43 ` Johannes Schindelin [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=e6d296ecf9f32f74c709714ca0de14ba@dscho.org \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=juston.h.li@gmail.com \
--cc=polynomial-c@gentoo.org \
--cc=stefan@agner.ch \
/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).