From: Taylor Blau <me@ttaylorr.com>
To: Christian Couder <christian.couder@gmail.com>
Cc: ZheNing Hu <adlternative@gmail.com>,
Junio C Hamano <gitster@pobox.com>,
Git List <git@vger.kernel.org>
Subject: Re: [QUESTION] how to diff one blob with nothing
Date: Fri, 4 Aug 2023 14:34:36 -0400 [thread overview]
Message-ID: <ZM1EvGVGv2ZYrpuT@nand.local> (raw)
In-Reply-To: <CAP8UFD2GV+1LhZDrSsgQ5=gRgYSTYsS36i2ugoBEHu-Oto-Sow@mail.gmail.com>
On Fri, Aug 04, 2023 at 10:28:53AM +0200, Christian Couder wrote:
> On Fri, Aug 4, 2023 at 6:42 AM ZheNing Hu <adlternative@gmail.com> wrote:
>
> > Actually, there is no need to support a default empty blob.
> > For example, with the command "git diff --no-index <file> /dev/null",
> > it can compare a file with /dev/null, but it can only compare <file>
> > and not <oid>.
> > Therefore, using commands like "git diff <oid> /dev/null",
> > "git diff --no-index <oid> /dev/null", or even "git diff <oid> --stdin"
> > could potentially solve this issue.
>
> Maybe it would be clearer to have a new option, called for example
> "--blob-vs-file", for that then. It could support both:
>
> $ git diff --blob-vs-file <blob> <file>
>
> and:
>
> $ git diff --blob-vs-file <file> <blob>
Hmm. This feels like a case of trying to teach 'git diff' to do too
much.
Thanks,
Taylor
next prev parent reply other threads:[~2023-08-04 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-19 9:59 [QUESTION] how to diff one blob with nothing ZheNing Hu
2023-07-19 16:15 ` Junio C Hamano
2023-07-26 18:00 ` ZheNing Hu
2023-07-26 18:23 ` Junio C Hamano
2023-07-27 17:46 ` Taylor Blau
2023-07-28 3:40 ` ZheNing Hu
2023-08-03 5:16 ` ZheNing Hu
2023-08-03 15:24 ` Taylor Blau
2023-08-04 2:28 ` ZheNing Hu
2023-08-04 8:28 ` Christian Couder
2023-08-04 18:34 ` Taylor Blau [this message]
2023-08-04 19:00 ` Junio C Hamano
2023-08-05 8:27 ` ZheNing Hu
2023-07-27 17:13 ` Konstantin Khomoutov
2023-07-28 3:35 ` ZheNing Hu
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=ZM1EvGVGv2ZYrpuT@nand.local \
--to=me@ttaylorr.com \
--cc=adlternative@gmail.com \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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).