From: Yuri Khan <yuri.v.khan@gmail.com>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: martin rudalics <rudalics@gmx.at>,
Andreas Schwab <schwab@linux-m68k.org>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: tabs, git diff and git apply
Date: Sun, 29 Nov 2020 16:56:24 +0700 [thread overview]
Message-ID: <CAP_d_8Wdd_JzPTEWqu9ogfEZ3bTDR_2+s3LbiVBFmxLBHCJYRw@mail.gmail.com> (raw)
In-Reply-To: <E1kjIle-0007Dn-9O@fencepost.gnu.org>
On Sun, 29 Nov 2020 at 16:13, Alfred M. Szmidt <ams@gnu.org> wrote:
> > Does `git
> > diff` have a configuration that is doing context diffs?
>
> Sure. You just have to be able to understand the doc.
>
> That is easy to verify, and you should be able to do
>
> HOME=/tmp git diff
>
> and see if the behaviour still is the same (if it doesn't work, just
> running as a different user should). If it isn't, it is a
> configuraiton setting that you have done -- reading the git-config man
> page would be the next action to see where such a setting is set.
Don’t bother. Git diff always does a unified diff.
next prev parent reply other threads:[~2020-11-29 9:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 9:29 tabs, git diff and git apply martin rudalics
2020-11-28 9:39 ` Andreas Schwab
2020-11-28 10:15 ` martin rudalics
2020-11-28 10:23 ` Andreas Schwab
2020-11-28 10:28 ` martin rudalics
2020-11-28 12:08 ` Andreas Schwab
2020-11-28 12:45 ` martin rudalics
2020-11-28 13:34 ` Andreas Schwab
2020-11-28 14:20 ` martin rudalics
2020-11-28 17:27 ` Alfred M. Szmidt
2020-11-28 18:23 ` martin rudalics
2020-11-28 18:52 ` Alfred M. Szmidt
2020-11-29 8:21 ` martin rudalics
2020-11-29 9:13 ` Alfred M. Szmidt
2020-11-29 9:52 ` martin rudalics
2020-11-29 9:56 ` Yuri Khan [this message]
2020-11-28 14:40 ` Stefan Monnier
2020-11-28 15:45 ` martin rudalics
2020-11-28 16:47 ` Stefan Monnier
2020-11-28 18:22 ` martin rudalics
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=CAP_d_8Wdd_JzPTEWqu9ogfEZ3bTDR_2+s3LbiVBFmxLBHCJYRw@mail.gmail.com \
--to=yuri.v.khan@gmail.com \
--cc=ams@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=rudalics@gmx.at \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.