From: "Catalin Marinas" <catalin.marinas@gmail.com>
To: "Karl Hasselström" <kha@treskal.com>
Cc: "Samuel Tardieu" <sam@rfc1149.net>, git@vger.kernel.org
Subject: Re: [StGIT PATCH] Do not insert an empty line before the diffstat info
Date: Tue, 5 Aug 2008 22:09:19 +0100 [thread overview]
Message-ID: <b0943d9e0808051409x1c9a9be3x68973c9ba5bdecc0@mail.gmail.com> (raw)
In-Reply-To: <20080804142000.GC12232@diana.vm.bytemark.co.uk>
2008/8/4 Karl Hasselström <kha@treskal.com>:
> On 2008-07-31 14:50:10 +0200, Samuel Tardieu wrote:
>
>> To make the format of stg output closer to the plain git one, do not
>> insert an empty line between the "---" separator and the diffstat
>> information.
>
> Thanks, will apply. (IMO it's slightly uglier, but it's better to be
> consistent. And it does save some space.)
Without this change, I could easily spot people posting patches with
StGIT rather than Git :-). Anyway, I'm OK with this patch as well.
Thanks.
--
Catalin
prev parent reply other threads:[~2008-08-05 21:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-31 12:50 [StGIT PATCH] Do not insert an empty line before the diffstat info Samuel Tardieu
2008-08-04 14:20 ` Karl Hasselström
2008-08-05 21:09 ` 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=b0943d9e0808051409x1c9a9be3x68973c9ba5bdecc0@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).