From: Tim Janik <timj@gnu.org>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: Overlong lines with git-merge --log
Date: Fri, 02 Nov 2012 14:24:29 +0100 [thread overview]
Message-ID: <5093C98D.90807@gnu.org> (raw)
In-Reply-To: <20121102100519.GC30221@sigill.intra.peff.net>
On 02.11.2012 11:05, Jeff King wrote:
> Taking just the first line of those often cuts off the useful part. It
> was deemed less bad to show the whole message as a subject rather than
> cut it off arbitrarily.
Thanks a lot for the explanation, I'm using git directly here, but the
two cases I had indeed lacked this newline.
--
Yours sincerely,
Tim Janik
---
http://timj.testbit.eu/ - Free software Author
next prev parent reply other threads:[~2012-11-02 13:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-02 1:30 Overlong lines with git-merge --log Tim Janik
2012-11-02 10:05 ` Jeff King
2012-11-02 13:24 ` Tim Janik [this message]
2012-11-02 13:49 ` Stephen Bash
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=5093C98D.90807@gnu.org \
--to=timj@gnu.org \
--cc=git@vger.kernel.org \
--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 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).