If you press `q' while selecting explicit deps, the patch is recorded
anyway.

    $ darcs --version
    1.0.8 (release)
    $ darcs --exact-version
    darcs compiled on Jul  4 2006, at 20:08:54
    # configured Fri Jun 16 14:55:21 EDT 2006
    ./configure --no-create --no-recursion

    Context:

    [TAG 1.0.8
    Tommy Pettersson <ptp@lysator.liu.se>**20060616160213]
    $ darcs init
    $ echo foo >foo
    $ darcs add foo
    $ darcs rec -am foo foo
    Recording changes in "foo":

    Finished recording patch 'foo'
    $ echo bar >bar
    $ darcs add bar
    $ darcs rec -am bar --ask-deps bar
    Recording changes in "bar":

    Thu Nov  2 03:31:47 EST 2006  Trent Buck <trentbuck@gmail.com>
      * foo
    Shall I depend on this patch? (1/?)  [ynWvpxqadjkc], or ? for help: q

    Depend on cancelled.
    Finished recording patch 'bar'
    $ darcs cha
    Thu Nov  2 03:32:09 EST 2006  Trent Buck <trentbuck@gmail.com>
      * bar

    Thu Nov  2 03:31:47 EST 2006  Trent Buck <trentbuck@gmail.com>
      * foo

I expected that the whole record operation to be aborted.

Is this the expected behaviour?  If so, what is the rationale for
behaving this way?
-- 
Trent Buck, Student Errant

On Wed, Nov 01, 2006 at 16:36:00 +0000, Trent Buck wrote:
> If you press `q' while selecting explicit deps, the patch is recorded
> anyway.

Thanks for your reports :-)

I guess it brings up the question, in the ask-deps query, do we want 'q'
to just mean "abort deps" or "abort the whole record?" Both seem
reasonable to me.

Although, from issue308 the former seems to confuse users.

Resolved in unstable with

Wed Jul 18 07:54:26 CEST 2007  Kevin Quick <quick@sparq.org>
  * Fix issue329: typing q for record --ask-deps records anyway with no deps.

Thanks!