From: Glenn Morris <rgm@gnu.org>
To: 13307@debbugs.gnu.org
Subject: bug#13307: log-edit-extract-headers can break a bzr repository
Date: Sun, 30 Dec 2012 03:41:01 -0500 [thread overview]
Message-ID: <i2a9swvso2.fsf@fencepost.gnu.org> (raw)
Package: emacs
Version: 24.2.91
Severity: important
I figured out how my recent bzr woes happened:
mkdir /tmp/foo
cd /tmp/foo
bzr init
touch file
bzr add file
bzr commit -m "commit"
echo foo >> file
emacs-24.2.91 -Q file &
C-x v v
In the vc-log buffer, enter the text between the --- lines below.
Note that the line immediately after the "Fixes:" line is not blank but
has an innocous single space character...
---
Fixes: debbugs:123
Commit message
---
This ends up passing: --fixes 'debbugs:123\n ' to bzr commit, and this
breaks bzr log.
next reply other threads:[~2012-12-30 8:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-30 8:41 Glenn Morris [this message]
2013-01-12 3:16 ` bug#13307: log-edit-extract-headers can break a bzr repository Stefan Monnier
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=i2a9swvso2.fsf@fencepost.gnu.org \
--to=rgm@gnu.org \
--cc=13307@debbugs.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).