When using push to a repository that has patches which the local repo does not
have, we are creating a version of the repo that has never existed. This might
be dangerous. Push already warns in that situation, but too late, after the
patches have been pushed. I think it should warn before selecting the patches:
Remote repository has 42 unpulled patches, do you still want to push there?

I could see this as being annoying (too many confirmation prompts!).  It sounds
like the best thing to do is to submit a patch and wait for the ensuing
discussion on darcs-users.

It would not change the number of confirmation prompts, just the order. You want
confirmation prompts which do not depend on the selected patches before the
selection mechanism (less chance for wasted selection work!). I cannot see how
it would not be a net gain.

Just to make things clearer: we would not need one more confirmation prompt
(contrarily to what I wrote originally). Just warn at the beginning of
patch-selection, and let people use 'q' there.

So the interaction would be:

Patch 1/42:
Description
Do you want to push that patch (note: remote repository has 1664 unpulled
patches) ?

Oh, I see what you mean.  No objections here.

The following patch updated the status of issue1308 to be resolved:

* resolve issue1308 push should warn about unpulled patches *before* patch-selection 
Ignore-this: 1f6fe64ad5cd84e7a8cae4261fcfa018