all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Philip Kaludercic <philipk@posteo.net>
Cc: Richard Stallman <rms@gnu.org>,
	 dgutov@yandex.ru, john@yates-sheets.org,  emacs-devel@gnu.org
Subject: Re: vc-find-revision-no-save?
Date: Sat, 29 Oct 2022 11:14:18 -0400	[thread overview]
Message-ID: <jwv5yg2is19.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <878rkz161j.fsf@posteo.net> (Philip Kaludercic's message of "Sat,  29 Oct 2022 06:46:00 +0000")

Philip Kaludercic [2022-10-29 06:46:00] wrote:
> Richard Stallman <rms@gnu.org> writes:
>> [[[ To any NSA and FBI agents reading my email: please consider    ]]]
>> [[[ whether defending the US Constitution against all enemies,     ]]]
>> [[[ foreign or domestic, requires you to follow Snowden's example. ]]]
>>
>>   > I can answer this one: because back when we wrote this code, the "Git"
>>   > of the day was called "CVS" and getting a historic revision required
>>   > fetching it from the centralized server, so you were usually quite happy
>>   > to keep a local copy, even if you had to erase them manually every once
>>   > in a while.
>>
>> I still sometimes use CVS, and this feature is still useful with it.
>
> In that case the suggestion to change the behaviour depending on the VCS
> should be fine.  If a VCS requires a network connection, storing the
> files locally can be helpful.

Note that, IIRC, the way the code works, if `vc-find-revision-no-save`
is non-nil you get an unsaved "file buffer", so it just takes a `C-x
C-s` to write the file to its "usual" place (i.e. `FILENAME.~REV~`,
IIRC) if you think it's worthwhile.

For that reason, I'm not convinced we need a special per-VCS handling
of this.


        Stefan




  parent reply	other threads:[~2022-10-29 15:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-24  0:27 vc-find-revision-no-save? John Yates
2022-10-24  9:42 ` vc-find-revision-no-save? Dmitry Gutov
2022-10-24 16:02   ` vc-find-revision-no-save? Philip Kaludercic
2022-10-24 17:14     ` vc-find-revision-no-save? Dmitry Gutov
2022-10-24 21:10     ` vc-find-revision-no-save? Stefan Monnier
2022-10-25  2:22       ` vc-find-revision-no-save? Eli Zaretskii
2022-10-28 21:57       ` vc-find-revision-no-save? Richard Stallman
2022-10-29  6:46         ` vc-find-revision-no-save? Philip Kaludercic
2022-10-29  7:07           ` vc-find-revision-no-save? Stefan Kangas
2022-10-29  9:18             ` vc-find-revision-no-save? Philip Kaludercic
2022-10-29  9:24           ` vc-find-revision-no-save? Andreas Schwab
2022-10-29  9:26             ` vc-find-revision-no-save? Philip Kaludercic
2022-10-29 15:14           ` Stefan Monnier [this message]
2022-10-29 15:40             ` vc-find-revision-no-save? Philip Kaludercic
2022-10-24 19:37 ` vc-find-revision-no-save? Juri Linkov
2022-10-24 20:00   ` vc-find-revision-no-save? John Yates
  -- strict thread matches above, loose matches on Subject: below --
2023-01-31 11:57 vc-find-revision-no-save? John Yates
2023-02-10 23:46 ` vc-find-revision-no-save? Dmitry Gutov
2023-03-27 19:38   ` vc-find-revision-no-save? John Yates
2023-03-27 20:50   ` vc-find-revision-no-save? John Yates

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=jwv5yg2is19.fsf-monnier+emacs@gnu.org \
    --to=monnier@iro.umontreal.ca \
    --cc=dgutov@yandex.ru \
    --cc=emacs-devel@gnu.org \
    --cc=john@yates-sheets.org \
    --cc=philipk@posteo.net \
    --cc=rms@gnu.org \
    /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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.