Isaac Dupree <[email protected]> writes:
> Petr Rockai wrote:
>> Ganesh Sittampalam <[email protected]> writes:
>>>> (It's quite likely there's something I don't understand about darcs, since
>>>> sometime I used 'darcs send' and it put some old draft patches of mine that
>>>> weren't in the current repo into the "context" of the patch, thus making
>>>> the
>>>> patches unusable by upstream.)
>>> This might be caused by a dependency of some form, or it might be caused by
>>> darcs send being too eager at picking up context. I'm not sure what darcs
>>> send
>>> does to decide what the context should be.
>> I think this is likely due to using -o/-O against a "wrong" repository
>> (a local branch with draft patches in it). By default, send works
>> against defaultrepo and if you use -o/-O, it is not clear that this is
>> not the one you intended.
>
> yes, there's a good chance that it was my silly error rather than
> darcs's. (I don't remember too well now.) defaultrepo is so
> hazardous...
I haven't tried it, but maybe you can do something like
ALL remote-repo "You forgot to specify a remote repo!"
so that _darcs/prefs/defaultrepo is overridden by a target repo that 1)
doesn't work; and 2) hopefully, reminds you why.
_______________________________________________
darcs-users mailing list
[email protected]
http://lists.osuosl.org/mailman/listinfo/darcs-users
