From: Stephen Bash <bash@genarts.com>
To: Tim Janik <timj@gnu.org>
Cc: git@vger.kernel.org, Jeff King <peff@peff.net>
Subject: Re: Overlong lines with git-merge --log
Date: Fri, 2 Nov 2012 09:49:33 -0400 (EDT) [thread overview]
Message-ID: <982632649.556351.1351864173516.JavaMail.root@genarts.com> (raw)
In-Reply-To: <5093C98D.90807@gnu.org>
----- Original Message -----
> From: "Tim Janik" <timj@gnu.org>
> Sent: Friday, November 2, 2012 9:24:29 AM
> Subject: Re: Overlong lines with git-merge --log
>
> 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.
FWIW we use merge --log quite extensively here at the office, and I've developed a habit to skim the extremely long lines and attempt to cut them intelligently (something I don't trust the computer to do for me). Sometimes that means taking the second or third sentence if it's a better summary, sometimes it's just abbreviating the first. Now that merge automatically spawns an editor, this is quite convenient (though it does take a bit longer).
Thanks,
Stephen
prev parent reply other threads:[~2012-11-02 13:49 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
2012-11-02 13:49 ` Stephen Bash [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=982632649.556351.1351864173516.JavaMail.root@genarts.com \
--to=bash@genarts.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=timj@gnu.org \
/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).