On Tue, Aug 24, 2010 at 08:49:26 +0000, Petr Ročkai wrote: > It may even break local lazy repos altogether, though. Please check the > above and also add tests for this behaviour (or point out that these > things are already covered by the testsuite and I am worrying > needlessly).
One more thing! (silly thing) Could you tweak your patch name so that
it starts with 'Resolve issue1923:'?
I'm always embarrassed to harp on this sort of thing, but last time I
spotted an extraneous space ("issue 1599"), bit my tongue and then later
regretted it when the dumb darcs-BTS integration failed to notice the
patch was applied. Having the automated BTS-darcs integration work
saves a lot of effort all around (*), particularly now that we're using
it for release management. The predictability also makes it easier for
humans to search for patches in the future.
One potentially useful hint: when I'm not sure about the exact syntax
for this sort of thing, I do an approximate search, eg.
darcs changes -i -p 'issue'
Which gives me examples to copy
Thanks!
Eric
(*) At least I hope so! But I think as a general rule, robots should
do as much of the dumb stuff as possible so that humans can spend
hacking Darcs instead of tweaking form entries.
Unfortunately, making robots smart enough to recognise, say the
difference between 'Resolve issue 1599' and 'Resolve issue1599'
(which is what bit me last time) takes some effort.
--
Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow>
For a faster response, try +44 (0)1273 64 2905 or
xmpp:[email protected] (Jabber or Google Talk only)
signature.asc
Description: Digital signature
_______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
