|
Created on 2007-08-23.09:13:08 by kowey, last changed 2009-08-27.14:07:21 by admin.
msg2092 (view) |
Author: kowey |
Date: 2007-08-23.09:12:47 |
|
See issue154
I wish darcs would detect when a patch was bad/unapplicable (for example, remove
a non-empty directory). Instead of blowing up, it would just refuse to pull the
patch.
I'm not sure if there is a practical way to do this. Darcs repair seems to do
it, but maybe it just conflates the-patch-is-bad with something-went-wrong.
|
msg2802 (view) |
Author: markstos |
Date: 2008-01-27.04:41:34 |
|
kowey,
Could you provide an example of the triggering behavior, or is really the same
issue as the "issue154" that you referenced?
Mark
|
msg2807 (view) |
Author: markstos |
Date: 2008-01-27.06:00:12 |
|
I'm going to go ahead and marked this as resolved-in-unstable, since it sounds
like the issue154 case, where directory-deleting/conflicting patches are handled
more gracefully now.
If there's a specific kind of other bad patch that darcs isn't handling
gracefully on pull, let's handle that as a new ticket.
|
|
Date |
User |
Action |
Args |
2007-08-23 09:13:14 | kowey | create | |
2008-01-27 04:41:35 | markstos | set | status: unread -> waiting-for nosy:
+ markstos messages:
+ msg2802 |
2008-01-27 06:00:14 | markstos | set | status: waiting-for -> resolved-in-unstable nosy:
droundy, tommy, beschmi, kowey, markstos, zooko topic:
+ Darcs2 messages:
+ msg2807 |
2008-09-04 21:31:24 | admin | set | status: resolved-in-unstable -> resolved nosy:
+ dagit |
2009-08-06 17:38:10 | admin | set | nosy:
+ jast, Serware, dmitry.kurochkin, darcs-devel, mornfall, simon, thorkilnaur, - droundy |
2009-08-06 20:34:57 | admin | set | nosy:
- beschmi |
2009-08-10 22:07:43 | admin | set | nosy:
- darcs-devel, jast, Serware, mornfall |
2009-08-11 00:02:07 | admin | set | nosy:
- dagit |
2009-08-25 17:51:47 | admin | set | nosy:
+ darcs-devel, - simon |
2009-08-27 14:07:21 | admin | set | nosy:
tommy, kowey, markstos, darcs-devel, zooko, thorkilnaur, dmitry.kurochkin |
|