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: Sun, 24 Nov 2024 04:15:11 -0000 (UTC)
Organization: PANIX Public Access Internet and UNIX, NYC
Message-ID: <vhu98f$93o$1@reader2.panix.com>
References: <vhr9ct$1dilp$1@dont-email.me> <vht6v1$1qfvl$1@dont-email.me> <vhtd6v$1rl0c$1@dont-email.me> <vhttf3$1u7an$1@dont-email.me>
Injection-Date: Sun, 24 Nov 2024 04:15:11 -0000 (UTC)
Injection-Info: reader2.panix.com; posting-host="spitfire.i.gajendra.net:166.84.136.80";
	logging-data="9336"; mail-complaints-to="abuse@panix.com"
X-Newsreader: trn 4.0-test77 (Sep 1, 2010)
Originator: cross@spitfire.i.gajendra.net (Dan Cross)
Bytes: 1947
Lines: 30

In article <vhttf3$1u7an$1@dont-email.me>,
Arne Vajhøj  <arne@vajhoej.dk> wrote:
>> There is no "client."  In a DVCS like git, when you commit a change,
>> everything is written locally.  Pushing to a server is an optional
>> separate operation and what you push is the version history that has
>> been written locally first.  There is never a point where the commit
>> message is sent over the network to another machine before being stored
>> as one component of a commit.
>
>OK. I am still thinking SVNish. Sorry.
>
>But does it matter?
>
>edit disk file--read disk file--write to local repo
>vs
>edit in memory--write to local repo
>
>still seem like a difference to me.

A difference yes, but why is it an interesting difference?
Aside from a "that's neat" how is this usefully different?

>Or is git external editor actual editing the final file
>inside the repo?

It edits a file that is in a known location in the repo, but
that is then folded into the commit.  It does not edit the final
committed artifact in the repo.

	- Dan C.