bug#1647: closed (vc-bzr commit bug on win32)

[GNU bug Tracking System]

Your message dated Tue, 18 Aug 2020 09:47:21 +0000
with message-id 
<CADwFkmk7KA0-pyTG=gc6PT_a7sA=ecMUvFWgR7Pw98pPtwJ3hw@mail.gmail.com>
and subject line Re: bug#1647: vc-bzr commit bug on win32
has caused the debbugs.gnu.org bug report #1647,
regarding vc-bzr commit bug on win32
to be marked as done.

(If you believe you have received this mail in error, please contact
help-debbugs@gnu.org.)


-- 
1647: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=1647
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems
> --- Begin Message ---
>
>
>
> Subject: 
>
> vc-bzr commit bug on win32
>
>
>
>
> Date: 
>
> Sat, 20 Dec 2008 13:02:43 +0800
>
>
>
>
> -----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-----
>
>
>
>
> --- End Message ---
> --- Begin Message ---
>
>
>
> Subject: 
>
> Re: bug#1647: vc-bzr commit bug on win32
>
>
>
>
> Date: 
>
> Tue, 18 Aug 2020 09:47:21 +0000
>
>
>
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > I just tried it, and didn't see any of these problems.  So either the
> > problem was fixed since then, or it was due to some local issue to
> > begin with.
>
> Thank you for checking.  I'm therefore closing this bug report.
>
> Best regards,
> Stefan Kangas
>
>
> --- End Message ---