conflicts on the last line of a file with no newline formatted wrongly
Bug #249077 reported by
Robert Collins
This bug report is a duplicate of:
Bug #36399: conflict markers at end of file without newline.
Edit
Remove
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
New
|
Undecided
|
Unassigned |
Bug Description
A conflict on the last line of a file with no newlines are formatted badly:
--
Foo\n
bar
--
conflicting with
--
Foo\n
bar\n
--
gave
--
Foo\n
<<<<<<\n
bar======\n
bar\n
>>>>>>\n
--
Not sure if we can do anything about this, but it seems desirable to have the === always against the left...
To post a comment you must log in.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Robert Collins wrote:
| Public bug reported:
|
| A conflict on the last line of a file with no newlines are formatted
badly:
| --
| Foo\n
| bar
| --
|
| conflicting with
| --
| Foo\n
| bar\n
| --
| gave
| --
| Foo\n
| <<<<<<\n
| bar======\n
| bar\n
|>>>>>> \n
| --
|
| Not sure if we can do anything about this, but it seems desirable to
| have the === always against the left...
|
| ** Affects: bzr
| Importance: Undecided
| Status: New
|
I think we had this reported in the past.
For the moment, it is the same as other systems like CVS.
One possibility is to do:
<<<<<<< TREE
bar\n
\\No trailing newline
=======\n
bar\n
|>>>>>> MERGE_SOURCE
That is somewhat less that fully desirable, but it might be better than
bar=======\n
John enigmail. mozdev. org
=:->
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://
iEYEARECAAYFAkh +DSAACgkQJdeBCY SNAANlAwCeNh08u Osg51gahQniFfYN GlEy fH4vYjIahHjW39J Qm8gVsEg
/b8AoLpS+
=/i+S
-----END PGP SIGNATURE-----