From: Junio C Hamano <gitster@pobox•com>
To: Linus Torvalds <torvalds@linux-foundation•org>
Cc: Git Mailing List <git@vger•kernel.org>
Subject: Re: Tabs in commit messages - de-tabify option in strbuf_stripspace()?
Date: Tue, 15 Mar 2016 17:45:21 -0700 [thread overview]
Message-ID: <xmqq4mc76yji.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <CA+55aFzHMp4hiCp7+2Yxy=KNQ_rBru3RM-pghXUPtoxr_L+w2w@mail.gmail.com> (Linus Torvalds's message of "Tue, 15 Mar 2016 17:16:57 -0700")
Linus Torvalds <torvalds@linux-foundation•org> writes:
> Do people hate that idea? I may not get around to it for a while (it's
> the kernel merge window right now), but I can write the patch
> eventually - I just wanted to do an RFC first.
Wouldn't it be nicer to do this kind of thing at the output side? A
stupid way would be to have an option to indent the log text with a
tab instead of 4-spaces, but a more sensible way would be to keep
the visual 4-space-indent and do the expand-tab for each line of
text.
That way, your viewing of existing commits that use 8-space HT to
align (and worse yet, mixture of 8-space HT and 8 spaces and assume
the end result would align in the output) would become more pleasant
without you having to run filter-branch ;-)
next prev parent reply other threads:[~2016-03-16 0:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 0:16 Tabs in commit messages - de-tabify option in strbuf_stripspace()? Linus Torvalds
2016-03-16 0:23 ` Stefan Beller
2016-03-16 0:45 ` Linus Torvalds
2016-03-16 0:34 ` Randall S. Becker
2016-03-16 0:45 ` Junio C Hamano [this message]
2016-03-16 0:48 ` Linus Torvalds
2016-03-16 1:00 ` Stefan Beller
2016-03-16 1:02 ` Stefan Beller
2016-03-16 14:27 ` Marc Branchaud
2016-03-16 14:50 ` Duy Nguyen
2016-03-16 16:15 ` Linus Torvalds
2016-03-16 16:47 ` Junio C Hamano
2016-03-20 13:29 ` Matthieu Moy
2016-03-16 4:05 ` Linus Torvalds
2016-03-16 4:46 ` Junio C Hamano
2016-03-16 4:57 ` Linus Torvalds
2016-03-16 5:17 ` Jeff King
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=xmqq4mc76yji.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=torvalds@linux-foundation$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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