Per David's comments, this is considered resolved-in-unstable, although it can
still be triggered with darcs-2 when run against repos that were originally
created with darcs 1 and the old repo format.
--
status: duplicate - resolved-in-unstable
__
Darcs
* David Roundy [EMAIL PROTECTED] [2008-01-11 12:42:31 -0500]:
Well, currently the conversion to darcs-2 requires a bottleneck, in which
only *one* repository is converted (i.e. all other branches get lopped
off). I think this is reasonable, as the transition to darcs-2 is always
going to
On Fri, Jan 11, 2008 at 08:43:13PM +0200, Tristan Seligmann wrote:
* David Roundy [EMAIL PROTECTED] [2008-01-11 12:42:31 -0500]:
Well, currently the conversion to darcs-2 requires a bottleneck, in which
only *one* repository is converted (i.e. all other branches get lopped
off). I think
New submission from Attila Lendvai [EMAIL PROTECTED]:
[EMAIL PROTECTED]:/tmp/ucw_ajax.clean$ darcs pull --no-set-default
../ucw_dev.clean
darcs-bin: bug in get_extra commuting patch:
Thu Aug 10 00:55:57 CEST 2006 [EMAIL PROTECTED]
* Refactored checkbox-field to use a hidden input and do not
