From: unobe@cpan.org
To: 9front@9front.org
Subject: Re: [9front] patch(1) filename detection
Date: Wed, 28 Sep 2022 23:47:56 -0700 [thread overview]
Message-ID: <FD7916DA7FA973C3B309FC93EFE3C687@smtp.pobox.com> (raw)
In-Reply-To: <6335318d.170a0220.77fb0.8d3c@mx.google.com>
Quoth Michael Forney <mforney@mforney.org>:
> However, longer term it might be worth supporting the
> git-diff extended header lines:
>
> deleted file mode <mode>
> new file mode <mode>
> old mode <mode>
> new mode <mode>
>
> There are also headers for renames and copies, but I don't think git
> or patch should bother with that, and should just present them as
> deleted and added files.
>
> Thoughts?
There's also:
similarity index <number>
dissimilarity index <number>
Would one (or both) of those be useful if we're now talking about
modes, too? Also, looking at the latest docs, I wasn't clear on what
the difference between 'deleted file mode', 'new file mode', 'old
mode', and 'new mode'. For a patch, what's the purpose of all four of
them? If a file is deleted, why isn't 'old mode' just used, and when
a file created, why isn't 'new mode' used?
The latest git docs also talk about combined diff mode, and it being
the default format with git-diff and git-show:
index <hash>,<hash>..<hash>
mode <mode>,<mode>..<mode>
new file mode <mode>
deleted file mode <mode>
That's not desired, right?
Reference: https://git-scm.com/docs/diff-format/2.37.2
prev parent reply other threads:[~2022-09-29 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-29 5:49 Michael Forney
2022-09-29 6:47 ` unobe [this message]
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=FD7916DA7FA973C3B309FC93EFE3C687@smtp.pobox.com \
--to=unobe@cpan.org \
--cc=9front@9front.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).