From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Samuel Tardieu" <sam@rfc1149.net>
Cc: kha@treskal.com, git@vger.kernel.org
Subject: Re: [StGIT v2 PATCH] Do not mess-up with commit message formatting when sending email
Date: Tue, 5 Aug 2008 21:48:27 +0100 [thread overview]
Message-ID: <b0943d9e0808051348x7130f26cy4a233ea35ee9a5d0@mail.gmail.com> (raw)
In-Reply-To: <20080804151913.4269.74254.stgit@dawn.rfc1149.net>
2008/8/4 Samuel Tardieu <sam@rfc1149.net>:
> The short description, which will be used as the email subject,
> gets its leading and trailing blanks removed.
>
> The long description gets its trailing blanks removed as well
> as any leading empty lines. Leading blanks are left untouched
> to preserve the formatting.
Thanks.
--
Catalin
prev parent reply other threads:[~2008-08-05 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 12:50 [StGIT PATCH] Do not mess-up with commit message formatting when sending email Samuel Tardieu
2008-08-04 14:16 ` Karl Hasselström
2008-08-04 15:19 ` [StGIT v2 " Samuel Tardieu
2008-08-04 15:57 ` Karl Hasselström
2008-08-05 20:48 ` Catalin Marinas [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=b0943d9e0808051348x7130f26cy4a233ea35ee9a5d0@mail.gmail.com \
--to=catalin.marinas@gmail.com \
--cc=git@vger.kernel.org \
--cc=kha@treskal.com \
--cc=sam@rfc1149.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 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).