From: norm@dad.org
To: l.s.r@web.de
Cc: git@vger.kernel.org, norm@dad.org
Subject: Re: Question: Getting 'git diff' to generate /usr/bin/diff output
Date: Sun, 17 Jul 2016 10:26:27 -0700 [thread overview]
Message-ID: <201607171726.u6HHQShO005227@shell1.rawbw.com> (raw)
In-Reply-To: Your message of "Sun, 17 Jul 2016 14:18:01 +0200." <578B7779.6090507@web.de>
<l.s.r@web.de> writes:
>
>The other replies covered how to use the system's own diff instead.
>Just curious: What makes using git diff difficult and its output hard to
>deal with for you?
In decreasing importance order:
I am 84 years old. I have been using /usr/bin/diff for more than four decades.
And having to learn how to read the output of 'git diff' makes learning how
to use git a more difficult trick for this old dog to learn. True, the diff of
today is very different from the diff of 1972, but the changes happened
gradually.
I have scripts which process the output of /usr/bin/diff.
'git diff' outputs escape characters which clutter my terminal. Yes, I can sed
them out, but then why are they there?
Norman Shapiro
next prev parent reply other threads:[~2016-07-17 17:26 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-16 19:12 Question: Getting 'git diff' to generate /usr/bin/diff output norm
2016-07-16 20:47 ` Perry Hutchison
2016-07-17 7:46 ` Johannes Schindelin
2016-07-19 15:20 ` norm
2016-07-17 12:18 ` René Scharfe
2016-07-17 17:26 ` norm [this message]
2016-07-18 7:23 ` Johannes Schindelin
2016-07-18 9:19 ` [PATCH] pager: disable color when pager is "more" Eric Wong
2016-07-18 13:16 ` Jeff King
2016-07-18 17:19 ` Junio C Hamano
2016-07-18 18:58 ` Jeff King
2016-07-19 2:37 ` Eric Wong
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201607171726.u6HHQShO005227@shell1.rawbw.com \
--to=norm@dad.org \
--cc=git@vger.kernel.org \
--cc=l.s.r@web.de \
/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 public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).