From: Eli Barzilay <email@example.com> To: Junio C Hamano <firstname.lastname@example.org> Cc: "René Scharfe" <email@example.com>, git <firstname.lastname@example.org> Subject: Re: git-diff bug? Date: Mon, 2 Nov 2020 22:14:07 -0500 [thread overview] Message-ID: <CALO-gusFac+GNrB9Rcbqteyv+gs5h0A-PTxnwRswZMhTnNBFyA@mail.gmail.com> (raw) In-Reply-To: <email@example.com> On Mon, Nov 2, 2020 at 5:15 PM Junio C Hamano <firstname.lastname@example.org> wrote: > > Eli Barzilay <email@example.com> writes: > > > How is it valid? > > Just this part. Any patch output that correctly explains how the > preimage text changed to the postimage text is a "valid" diff, and > that is how René used the word. To be clear, the "valid" in my question is about the correctness of the expected behavior, which (as I disclaimed) is likely a problem of the text that explains these expectations. If validity is only about the correctness of the resulting transform, then it is obviously valid, as well as the other alternatives that you included (and therefore this is not the meaning that I used, otherwise I wouldn't have sent this). In any case, I think that I now see the problem: the (sparse) explanation says "Ignore changes whose lines are all blank.". It would have been helpful to clarify with "(but blank likes that are *part of* a change are still shown)". Thanks, -- ((x=>x(x))(x=>x(x))) Eli Barzilay: http://barzilay.org/ Maze is Life!
next prev parent reply other threads:[~2020-11-03 3:14 UTC|newest] Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-11-02 6:53 Eli Barzilay 2020-11-02 17:45 ` René Scharfe 2020-11-02 21:06 ` Eli Barzilay 2020-11-02 22:14 ` Junio C Hamano 2020-11-03 3:14 ` Eli Barzilay [this message] 2020-11-03 16:58 ` Junio C Hamano 2020-11-02 22:00 ` Junio C Hamano
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=CALO-gusFac+GNrB9Rcbqteyv+gs5h0A-PTxnwRswZMhTnNBFyA@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: git-diff bug?' \ /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
Code repositories for project(s) associated with this 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).