From: Michael J Gruber <git@drmicha•warpmail.net>
To: Junio C Hamano <junio@pobox•com>
Cc: Jonathan Nieder <jrnieder@gmail•com>,
Jay Soffian <jaysoffian@gmail•com>,
git@vger•kernel.org
Subject: Re: [PATCH] Add log.abbrev-commit config option
Date: Mon, 16 May 2011 10:24:14 +0200 [thread overview]
Message-ID: <4DD0DF2E.5070901@drmicha.warpmail.net> (raw)
In-Reply-To: <7vliy8rawv.fsf@alter.siamese.dyndns.org>
Junio C Hamano venit, vidit, dixit 15.05.2011 03:48:
> Jonathan Nieder <jrnieder@gmail•com> writes:
>
>> Hm, that wouldn't have been my hunch. Are you aware of any scripts
>> that parse "git whatchanged" output?
>>
>> More worrying is "git log --format=raw".
>
> Both are very sane worries. I am not interested at all in queuing this
> change without any careful migration consideration.
>
> Thanks.
Another instance of "config for option". Note that, again, it has the
same potential problems as a general approach...
Michael
prev parent reply other threads:[~2011-05-16 8:24 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-14 17:22 [PATCH] Add log.abbrev-commit config option Jay Soffian
2011-05-14 17:26 ` Jay Soffian
2011-05-14 19:01 ` Jonathan Nieder
2011-05-14 19:35 ` Jay Soffian
2011-05-14 20:19 ` [PATCH] add, merge, diff: do not use strcasecmp to compare config variable names Jonathan Nieder
2011-05-15 1:53 ` Junio C Hamano
2011-05-14 20:47 ` [PATCH v2] Add log.abbrevCommit config variable Jay Soffian
2011-05-14 21:55 ` Jonathan Nieder
2011-05-14 22:22 ` Jay Soffian
2011-05-14 22:49 ` [PATCH v3] " Jay Soffian
2011-05-15 13:25 ` Jay Soffian
2011-05-15 22:42 ` Junio C Hamano
2011-05-16 5:53 ` Jay Soffian
2011-05-16 7:00 ` Jonathan Nieder
2011-05-16 7:18 ` Jay Soffian
2011-05-17 17:03 ` Junio C Hamano
2011-05-17 21:50 ` Junio C Hamano
2011-05-18 1:05 ` Jay Soffian
2011-05-17 18:50 ` Junio C Hamano
2011-05-17 19:08 ` Jay Soffian
2011-05-15 1:48 ` [PATCH] Add log.abbrev-commit config option Junio C Hamano
2011-05-16 8:24 ` Michael J Gruber [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=4DD0DF2E.5070901@drmicha.warpmail.net \
--to=git@drmicha$(echo .)warpmail.net \
--cc=git@vger$(echo .)kernel.org \
--cc=jaysoffian@gmail$(echo .)com \
--cc=jrnieder@gmail$(echo .)com \
--cc=junio@pobox$(echo .)com \
/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