[tahoe-lafs-trac-stream] [tahoe-lafs] #1120: simplify Unicode support by assuming that argv and output encodings are the same

[tahoe-lafs]

#1120: simplify Unicode support by assuming that argv and output encodings are the
same
----------------------------+-----------------------------
     Reporter:  davidsarah  |      Owner:  zooko
         Type:  defect      |     Status:  closed
     Priority:  minor       |  Milestone:  1.9.0
    Component:  code        |    Version:  1.7.0
   Resolution:  fixed       |   Keywords:  unicode cleanup
Launchpad Bug:              |
----------------------------+-----------------------------

Comment (by davidsarah):

 [http://irclog.perlgeek.de/darcs/2011-07-28#i_4179335 Heffalump wrote] in
 #darcs:
 > darcs applies patches in the order listed.

 > a replace patch on its own does exactly what it says on the tin  - it
 replaces token A with token B in the file listed

 > so if you have hunk patches then a replace patch, the hunk patches
 happen first then the replace

 > in your example I think force must have been used to do a couple of
 replace operations. I'm not entirely sure, but perhaps output -> argv was
 done first then argv -> io, or something like that.

 > with --force, if you are renaming A to B, then --force first inserts
 hunks that change any existing Bs to A, then a replace patch from A to B.
 That's to ensure that everything is invertible.

 > because darcs tries to squish together individual pieces of patches in a
 single named patch to avoid redundant operations, I can imagine replace
 --force twice generting something like you describe.

-- 
Ticket URL: <http://tahoe-lafs.org/trac/tahoe-lafs/ticket/1120#comment:11>
tahoe-lafs <http://tahoe-lafs.org>
secure decentralized storage