From: 马旋（SuperMMX） <supermmx@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#1647: vc-bzr commit bug on win32
Date: Sat, 20 Dec 2008 13:02:43 +0800 [thread overview]
Message-ID: <20081220130243.4821ebf0.SuperMMX@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Problem:
Emacs : GNU Emacs 23.0.60.1 (i386-mingw-nt5.1.2600) of 2008-12-09
Bazaar : Bazaar (bzr) 1.10 (Python installation)
1) In vc-dired, there are more than one file modified, mark some of them,
and do commit, all the files get committed, not only the marked ones.
2) If the commit comment has more than one lines, only the first one
is passed to Bazaar, and all the files get committed.
It seems that this is related with \n in commit comment (no matter one line
or multi-line).
But there is no problem under Linux.
Anyone met this problem ?
Thanks
- --
A. Because it makes the logic of the discussion difficult to follow.
Q. Why shoudn't I top post?
A. No.
Q Should I top post?
A: Because it destroys the flow of the conversation
Q: Why is it bad?
A: No, it's bad.
Q: Should I top post in replies to mailing lists?
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (MingW32)
iEYEARECAAYFAklMfHQACgkQYjhzyV/TMxsW4gCdF7a8epi/2wyq+Q1ijo/E1CqP
IywAn3K7IV3ucwPnEBHsRhURT4PdWkDJ
=pJMA
-----END PGP SIGNATURE-----
next reply other threads:[~2008-12-20 5:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-20 5:02 马旋（SuperMMX） [this message]
2020-08-17 22:23 ` bug#1647: vc-bzr commit bug on win32 Stefan Kangas
2020-08-18 1:28 ` 马旋（MA Xuan）
2020-08-18 4:28 ` Eli Zaretskii
2020-08-18 9:47 ` Stefan Kangas
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=20081220130243.4821ebf0.SuperMMX@gmail.com \
--to=supermmx@gmail.com \
--cc=1647@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@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).