From: Tommy Thorn <tommy-git@thorn.ws>
To: Sergei Organov <osv@javad.com>
Cc: Alexandre Julliard <julliard@winehq.org>, git@vger.kernel.org
Subject: Re: [PATCH 3/4] git.el: Check for existing buffers on revert.
Date: Fri, 08 Feb 2008 21:41:16 -0800 [thread overview]
Message-ID: <47AD3CFC.7090401@thorn.ws> (raw)
In-Reply-To: <87prv7z84i.fsf@osv.gnss.ru>
Sergei Organov wrote:
> BTW, there is another related issue: what to do with buffers for which their
> files disappear (are removed). AFAIK PCVS doesn't close such buffers,
> that according to the above logic is confusing as well.
>
Please don't revert such buffers! More than once have I been saved from
a blunder by the fact that Emacs still had a copy of the accidentally
erase/overwritten file. The normal Emacs behaviour is to prompt upon
editing whether to edit the buffer since the file has changed.
Thanks
Tommy
prev parent reply other threads:[~2008-02-09 5:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-07 12:51 [PATCH 3/4] git.el: Check for existing buffers on revert Alexandre Julliard
2008-02-08 14:30 ` Sergei Organov
2008-02-08 14:54 ` Alexandre Julliard
2008-02-08 17:10 ` Sergei Organov
2008-02-09 5:41 ` Tommy Thorn [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=47AD3CFC.7090401@thorn.ws \
--to=tommy-git@thorn.ws \
--cc=git@vger.kernel.org \
--cc=julliard@winehq.org \
--cc=osv@javad.com \
/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).