[darcs-devel] [issue862] Output patch format depends on patch origin for hashed repos!

[Ben Coburn]

New submission from Ben Coburn <btcoburn at silicodon.net>:

Sometimes patches with one "atomic change" have curly braces and sometimes they
don't. Specificaly, patches imported with 'darcs get --hashed' retain curly
braces, while patches newly created in the hashed repository are not represented
with curly braces.

See the following example. The first two patches were imported with 'darcs get
--hashed', while the second two patches were created directly in the hashed
repository.

[test setup
test at example.com**20080518153437] {
addfile ./baz
hunk ./baz 1
+test setup again
}

[patch format test
test at example.com**20080518153518] {
hunk ./baz 2
+darcs1 test one hunk
+
}

[local one hunk
test at example.com**20080518173216] hunk ./baz 3
+
+one hunk locally recorded in darcs2

[two hunk local patch
test at example.com**20080518173647] {
hunk ./baz 1
-test setup again
+test setup
hunk ./baz 4
-one hunk locally recorded in darcs2
+two hunk locally recorded in darcs2
}

Darcs 2.0.0 stable release binary for MacOS X. Patches were listed with 'darcs
send -o'.

----------
messages: 4751
nosy: Serware, beschmi, btcoburn, dagit, tommy
priority: bug
status: unread
title: Output patch format depends on patch origin for hashed repos!
topic: Darcs2

__________________________________
Darcs bug tracker <bugs at darcs.net>
<http://bugs.darcs.net/issue862>
__________________________________