Sat Jan  9 21:43:41 EST 2010  Daniel Dickison <danieldickison@gmail.com>
  * Accept issue1726: Files with _darcs prefix are always boring

Attachments

• accept-issue1726_-files-with-_darcs-prefix-are-always-boring.dpatch
• unnamed

If I may just assign this one to you, Trent.

[Accept issue1726: Files with _darcs prefix are always boring
Daniel Dickison <danieldickison@gmail.com>**20100110024341
 Ignore-this: 872c208940145e91aa323ebf0d3b342e
] addfile ./tests/failing-issue1726_darcs_always-boring.sh
hunk ./tests/failing-issue1726_darcs_always-boring.sh 1
+touch _darcsfoo
+
+# Passing --boring should definitely not fail.
+darcs whatsnew -ls --boring
+darcs add --boring _darcsfoo
+
+# Without --boring, it should succeed given the default boring file.
+darcs whatsnew -ls
+darcs add _darcsfoo

The second add will fail with a "The following file is already in the repository" warning.

I meant to send an amended patch, but it got filed as a separate patch (patch135).  
Sorry for the confusion.  What is the right way to tell the tracker to amend the 
patch attached in this thread?

Not a problem.  Have a look at http://wiki.darcs.net/Development/PatchTracker
for future amendments.

In the meantime, you can just set the status to obsoleted and add the new patch
as a superseder to this one.