From mboxrd@z Thu Jan  1 00:00:00 1970
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=0.0 required=5.0 tests=DKIM_SIGNED,DKIM_VALID
	autolearn=ham autolearn_force=no version=3.4.4
Received: (qmail 3286 invoked from network); 29 Sep 2022 06:49:51 -0000
Received: from 9front.inri.net (168.235.81.73)
  by inbox.vuxu.org with ESMTPUTF8; 29 Sep 2022 06:49:51 -0000
Received: from pb-smtp2.pobox.com ([64.147.108.71]) by 9front; Thu Sep 29 02:48:03 -0400 2022
Received: from pb-smtp2.pobox.com (unknown [127.0.0.1])
	by pb-smtp2.pobox.com (Postfix) with ESMTP id 3954714B80A
	for <9front@9front.org>; Thu, 29 Sep 2022 02:47:59 -0400 (EDT)
	(envelope-from unobe@cpan.org)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h=message-id
	:to:subject:date:from:in-reply-to:mime-version:content-type
	:content-transfer-encoding; s=sasl; bh=omIESKeQMQrlLlnvrHa12WH8A
	A/Y+aMKvEr2aKY3RzQ=; b=kxF5BM8jaVJ1/emT+loG0CexmoINNqrNKT2wExQ4n
	vG6z7Veu7/hPXK8yu4zD7gOUnaCj5p88yMcEvLJIL1Dx3umOBNxcb1+iajeMg7FF
	vlvjXIrSlL/ObJhivtvv4RB/3k1gXrtoyzhnwxzFiorwVHa0vCG7j18E/v1VicxT
	kg=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1])
	by pb-smtp2.pobox.com (Postfix) with ESMTP id 20C2B14B806
	for <9front@9front.org>; Thu, 29 Sep 2022 02:47:59 -0400 (EDT)
	(envelope-from unobe@cpan.org)
Received: from strider.localdomain (unknown [75.237.206.13])
	(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
	(No client certificate requested)
	by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 4E9E914B805
	for <9front@9front.org>; Thu, 29 Sep 2022 02:47:58 -0400 (EDT)
	(envelope-from unobe@cpan.org)
Message-ID: <FD7916DA7FA973C3B309FC93EFE3C687@smtp.pobox.com>
To: 9front@9front.org
Date: Wed, 28 Sep 2022 23:47:56 -0700
From: unobe@cpan.org
In-Reply-To: <6335318d.170a0220.77fb0.8d3c@mx.google.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
Content-Transfer-Encoding: 7bit
X-Pobox-Relay-ID:
 A77941C0-3FC2-11ED-BD84-307A8E0A682E-09620299!pb-smtp2.pobox.com
List-ID: <9front.9front.org>
List-Help: <http://lists.9front.org>
X-Glyph: ➈
X-Bullshit: virtual advanced XML table NoSQL software scripting locator 
Subject: Re: [9front] patch(1) filename detection
Reply-To: 9front@9front.org
Precedence: bulk

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