From: Dan Nicolaescu <dann@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 6028@debbugs.gnu.org
Subject: bug#6028: 24.0.50; HELLO wants "C-x v v"
Date: Sat, 24 Apr 2010 15:32:58 -0400 [thread overview]
Message-ID: <yxq7hnw63yt.fsf@fencepost.gnu.org> (raw)
In-Reply-To: <83eii510po.fsf@gnu.org> (Eli Zaretskii's message of "Sat\, 24 Apr 2010 15\:42\:11 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> This bug report will be sent to the Free Software Foundation,
> not to your local site managers!
> Please write in English if possible, because the Emacs maintainers
> usually do not have translators to read other languages for them.
>
> Your bug report will be posted to the bug-gnu-emacs@gnu.org mailing list,
> and to the gnu.emacs.bug news group.
>
> Please describe exactly what actions triggered the bug
> and the precise symptoms of the bug. If you can, give
> a recipe starting from `emacs -Q':
>
> Inside an Emacs bzr branch:
>
> emacs -Q
> C-h H
> C-x C-q
>
> The last command causes Emacs to display the following bogus message:
>
> File is under version-control; use C-x v v to check in/out
>
> The buffer becomes writable, nonetheless, as expected.
If this is in an uninstalled tree, then C-h H opens the HELLO file that is managed by bzr.
The message that you see is what VC says when you try to make writable a file managed by VC.
Is that the issue here?
next prev parent reply other threads:[~2010-04-24 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-24 12:42 bug#6028: 24.0.50; HELLO wants "C-x v v" Eli Zaretskii
2010-04-24 19:32 ` Dan Nicolaescu [this message]
2010-04-24 20:40 ` Eli Zaretskii
2010-04-25 3:05 ` Dan Nicolaescu
2010-04-25 13:19 ` Stefan Monnier
2010-04-25 19:20 ` Dan Nicolaescu
2010-04-25 19:40 ` Eli Zaretskii
2010-04-26 14:25 ` Stefan Monnier
2010-04-25 13:45 ` Eli Zaretskii
2011-07-13 18:08 ` Lars Magne Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=yxq7hnw63yt.fsf@fencepost.gnu.org \
--to=dann@gnu.org \
--cc=6028@debbugs.gnu.org \
--cc=eliz@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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).