Comment 14 for bug 710410
Revision history for this message
| Gordon Tyler (doxxx) wrote Re: [Bug 710410] Re: "Parsing failed" on uncommit if contents of commit message are nonstandard | #14 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
bbfa235
(Get the code!)
On Mon, January 31, 2011 10:48 am, Pat Tressel wrote:
> Aha -- I see people have already made the suggestions below. (I'm using
> gmail and it started a fresh thread due to the new subject. ;-) The only
> ones that remain are a) perhaps ask the user if they intended that
> message,
> and b) if it's also in the repository, might need to deal w/ it there, at
> least to prevent it from being brought back into branch.conf as
> un-escaped/
As I understand it, the copy in branch.conf is only kept there temporarily
to remember what the last commit message was, so that the commit command
can offer the same message when re-committing an uncommitted revision, for
example. It has no relation to how the commit message is actually stored
in the branch revision data.