Re: in-memory editing with EDT or EVE

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.