git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Johannes Sixt <j6t@kdbg.org>
Cc: Junio C Hamano <gitster@pobox.com>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	git@vger.kernel.org
Subject: Re: [PATCH 1/4] diff/xdiff: refactor EOF-EOL detection
Date: Sun, 6 Jun 2010 18:08:00 -0400	[thread overview]
Message-ID: <20100606220800.GD6993@coredump.intra.peff.net> (raw)
In-Reply-To: <201006061101.02156.j6t@kdbg.org>

On Sun, Jun 06, 2010 at 11:01:02AM +0200, Johannes Sixt wrote:

> > Peff uses --textconv to show changes to the exif information on his
> > photo collections.  If he has any symlinks, and if he finds that
> > removal of "\No newline" is a regression and not an improvement,
> > what recourse does your patch give him?  Saying --no-textconv to
> > work around that regression is not a solution, isn't it?
> 
> Oh, I'm pretty sure that Peff wouldn't use --textconv on his
> repository if he cared that diffs contained complete reproducible
> information.

How did my name get dragged into this? ;P

No, I wouldn't use textconv if I cared that my diffs contained complete
reproducible information. But I think Junio's point is that the presence
of that information is valuable to some users to read, regardless of
applying patches. That is, I took his message to mean that he would want
to have this feature off, even for human viewing of the diff. And there
would be no way to turn off this feature, but not textconv.

I don't necessarily agree with that; I don't personally care when
viewing a symlink diff whether that line is there or not. But if there
are people who do, then you have left them with no way out.

-Peff

  reply	other threads:[~2010-06-06 22:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-06-03 14:35 [PATCH 0/4] Don't warn about missing EOL for symlinks Michael J Gruber
2010-06-03 14:35 ` [PATCH 1/4] diff/xdiff: refactor EOF-EOL detection Michael J Gruber
2010-06-03 21:58   ` Junio C Hamano
2010-06-04  7:38     ` Michael J Gruber
2010-06-05  6:38       ` Junio C Hamano
2010-06-05 18:58         ` Michael J Gruber
2010-06-06 22:03         ` Jeff King
2010-06-06  4:00       ` Junio C Hamano
2010-06-06  9:01         ` Johannes Sixt
2010-06-06 22:08           ` Jeff King [this message]
2010-06-07  8:10           ` Michael J Gruber
2010-06-03 14:35 ` [PATCH 2/4] diff: make treatment of missing EOL at EOF configurable Michael J Gruber
2010-06-03 14:35 ` [PATCH 3/4] diff: Do not warn about missing EOL at EOF for symlinks Michael J Gruber
2010-06-03 17:02   ` Jeff King
2010-06-03 14:35 ` [PATCH 4/4] RFC: add whitespace rule for no-eol-at-eof Michael J Gruber
2010-06-03 14:47 ` [PATCH 0/4] Don't warn about missing EOL for symlinks Matthieu Moy
2010-06-03 14:57   ` Michael J Gruber
2010-06-03 17:07     ` Jeff King
2010-06-03 19:55       ` Michael J Gruber
2010-06-03 20:17         ` Jeff King
2010-06-04 14:15       ` Johannes Sixt
2010-06-04 15:25         ` 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=20100606220800.GD6993@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=j6t@kdbg.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).