darcs

Patch 133 Accept issue1726: Files with _darcs prefix are always ...

Title Accept issue1726: Files with _darcs prefix are always ...
Superseder Accept issue1726: Files with _darcs prefix are always ...
View: 135
Nosy List danieldickison, darcs-users, davidm, kowey, twb
Related Issues
Status obsoleted Assigned To twb
Milestone

Created on 2010-01-10.10:32:15 by danieldickison, last changed 2011-05-10.19:36:14 by darcswatch. Tracked on DarcsWatch.

Files
File name Status Uploaded Type Edit Remove
accept-issue1726_-files-with-_darcs-prefix-are-always-boring.dpatch danieldickison, 2010-01-10.10:32:14 text/x-darcs-patch
unnamed danieldickison, 2010-01-10.10:32:14 text/plain
See mailing list archives for discussion on individual patches.
Messages
msg9768 (view) Author: danieldickison Date: 2010-01-10.10:32:14
Sat Jan  9 21:43:41 EST 2010  Daniel Dickison <danieldickison@gmail.com>
  * Accept issue1726: Files with _darcs prefix are always boring
Attachments
msg9771 (view) Author: kowey Date: 2010-01-10.11:52:12
If I may just assign this one to you, Trent.
msg9782 (view) Author: davidm Date: 2010-01-11.20:50:36
[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.
msg9784 (view) Author: danieldickison Date: 2010-01-11.21:08:43
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?
msg9785 (view) Author: kowey Date: 2010-01-11.21:29:05
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.
History
Date User Action Args
2010-01-10 10:32:15danieldickisoncreate
2010-01-10 10:33:31darcswatchsetdarcswatchurl: http://darcswatch.nomeata.de/repo_http:__darcs.net_.html#bundle-a9ed1cb5a135cb2e22e2d131f021ce83a31ff896
2010-01-10 11:52:12koweysetnosy: + kowey, twb
messages: + msg9771
assignedto: twb
2010-01-11 20:50:37davidmsetnosy: + davidm
messages: + msg9782
2010-01-11 21:08:43danieldickisonsetmessages: + msg9784
2010-01-11 21:29:06koweysetstatus: needs-review -> obsoleted
superseder: + Accept issue1726: Files with _darcs prefix are always ...
messages: + msg9785
2011-05-10 19:36:14darcswatchsetdarcswatchurl: http://darcswatch.nomeata.de/repo_http:__darcs.net_.html#bundle-a9ed1cb5a135cb2e22e2d131f021ce83a31ff896 -> http://darcswatch.nomeata.de/repo_http:__darcs.net_reviewed.html#bundle-a9ed1cb5a135cb2e22e2d131f021ce83a31ff896