Path: ...!news.misty.com!weretis.net!feeder9.news.weretis.net!panix!.POSTED.spitfire.i.gajendra.net!not-for-mail
From: cross@spitfire.i.gajendra.net (Dan Cross)
Newsgroups: comp.os.vms
Subject: Re: in-memory editing with EDT or EVE
Date: Sat, 23 Nov 2024 14:30:03 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <vhsotb$rki$1@reader2.panix.com>
References: <vhr9ct$1dilp$1@dont-email.me> <vhrd3u$1dqca$3@dont-email.me> <vhsm4i$1nfvc$1@dont-email.me>
Injection-Date: Sat, 23 Nov 2024 14:30:03 -0000 (UTC)
Injection-Info: reader2.panix.com; posting-host="spitfire.i.gajendra.net:166.84.136.80";
	logging-data="28306"; mail-complaints-to="abuse@panix.com"
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: cross@spitfire.i.gajendra.net (Dan Cross)
Bytes: 1520
Lines: 18

In article <vhsm4i$1nfvc$1@dont-email.me>,
Craig A. Berry <craigberry@nospam.mac.com> wrote:
>On 11/22/24 8:02 PM, Lawrence D'Oliveiro wrote:
>> On Fri, 22 Nov 2024 19:59:07 -0500, Arne Vajhøj wrote:
>> 
>>> But this is what a source control system really should be using for such
>>> functionality. No need for temporary disk files.
>> 
>> On Linux systems at least, temporary files are usually created in /tmp,
>> and distros commonly mount an instance of tmpfs on that, so no actual disk
>> files need be created.
>
>But that is not what git does when staging a commit.

Regardless of that, it is what git does when composing a commit
message.

	- Dan C.