From: Thomas Rast <trast@student.ethz.ch>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Thomas Rast <trast@student.ethz.ch>, Git List <git@vger.kernel.org>
Subject: Re: Proposal: sharing .git/config
Date: Tue, 19 Feb 2013 11:39:17 +0100 [thread overview]
Message-ID: <87vc9osi3u.fsf@pctrast.inf.ethz.ch> (raw)
In-Reply-To: <CALkWK0m--MbtNzGH9hNPCCLJWhv6rjF9Y=WQ4qnHUFnE61p6kw@mail.gmail.com> (Ramkumar Ramachandra's message of "Tue, 19 Feb 2013 15:54:32 +0530")
Ramkumar Ramachandra <artagnon@gmail.com> writes:
> Thomas Rast wrote:
>> Ramkumar Ramachandra <artagnon@gmail.com> writes:
>>> There are also other things in .git/config that would be nice to
>>> share, like whether to do a --word-diff (why isn't it a configuration
>>> variable yet?)
>>
>> Because that would break pretty much every script that uses git-diff?
>
> diff.c already makes a differentiation between git_diff_ui_config()
> and git_diff_basic_config(); there are configuration options that
> should only be applied when the command is called interactively.
It still breaks every other use of diff unless you make the diff output
depend on whether the user runs directly at the terminal (possibly using
git's own paging).
For example, if you just say something like 'git diff >file' for
inclusion in an email, you expect that to be a git-apply compatible
diff.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-02-19 10:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 9:25 Proposal: sharing .git/config Ramkumar Ramachandra
2013-02-19 10:03 ` Thomas Rast
2013-02-19 10:24 ` Ramkumar Ramachandra
2013-02-19 10:39 ` Thomas Rast [this message]
2013-02-19 10:34 ` Duy Nguyen
2013-02-19 15:36 ` Jeff King
2013-03-11 19:31 ` Ramkumar Ramachandra
2013-03-12 8:53 ` Jeff King
2013-03-18 9:00 ` Ramkumar Ramachandra
2013-03-18 11:48 ` Jeff King
2013-02-19 14:38 ` Adam Spiers
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=87vc9osi3u.fsf@pctrast.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.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).