From: Eli Zaretskii <eliz@gnu.org>
To: Reuben Thomas <rrt@sc3d.org>
Cc: 8159@debbugs.gnu.org
Subject: bug#8159: file-name-sans-version fails for some git files
Date: Thu, 03 Mar 2011 08:57:25 -0500 [thread overview]
Message-ID: <E1Pv91x-0007zE-PA@fencepost.gnu.org> (raw)
In-Reply-To: <AANLkTi=NMYp95dSvkeLKS2QX8=iMyNcgaXEs1ak97FsD@mail.gmail.com> (message from Reuben Thomas on Thu, 3 Mar 2011 13:39:32 +0000)
> Date: Thu, 3 Mar 2011 13:39:32 +0000
> From: Reuben Thomas <rrt@sc3d.org>
> Cc: 8159@debbugs.gnu.org
>
> On 3 March 2011 13:36, Eli Zaretskii <eliz@gnu.org> wrote:
> >
> > If you are okay with having foo.js~ as a simple backup file name of
> > foo.js.~HEAD~1~ and foo.js.~3~ as its numbered backup, then I see no
> > issues here. I just wonder if that would surprise git users (I don't
> > use it too much, so I don't know).
>
> Why would you have a backup of such a file?
Because vc-make-backup-files is set non-nil?
> It's a file visited with
> vc-revision-other-window, which is by default read-only.
Is that the only way to visit files with such names?
Anyway, your change is not limited to this particular situation, it is
more general. It will affect any file of that form, anywhere.
next prev parent reply other threads:[~2011-03-03 13:57 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-02 22:31 bug#8159: file-name-sans-version fails for some git files Reuben Thomas
2011-03-03 3:58 ` Eli Zaretskii
2011-03-03 12:02 ` Reuben Thomas
2011-03-03 13:36 ` Eli Zaretskii
2011-03-03 13:39 ` Reuben Thomas
2011-03-03 13:57 ` Eli Zaretskii [this message]
2011-03-03 14:00 ` Reuben Thomas
2011-03-03 15:09 ` Andreas Schwab
2011-03-03 15:26 ` Reuben Thomas
2011-03-03 16:23 ` Andreas Schwab
2011-03-03 22:58 ` Reuben Thomas
2011-03-04 7:55 ` Eli Zaretskii
2011-03-05 16:42 ` Reuben Thomas
2011-03-05 17:00 ` Eli Zaretskii
2011-03-05 20:36 ` Chong Yidong
2011-03-03 14:33 ` Andreas Schwab
2011-03-03 14:35 ` Reuben Thomas
2011-03-03 14:45 ` Andreas Schwab
2011-03-03 14:53 ` Reuben Thomas
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=E1Pv91x-0007zE-PA@fencepost.gnu.org \
--to=eliz@gnu.org \
--cc=8159@debbugs.gnu.org \
--cc=rrt@sc3d.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.