This patch isn't ideal since dist --index behaves different than for
example changes --index or annotate --index; in changes and annotate
--index 1 gives you the latest patch and --index 0 is either unspecified
or the same as --index 1 whereas dist --index 0 (with this patch) 
creates a tarball with all patches and --index 1 with all patches minus
the latest.
dist --index <maxPatchCount> creates a tarball containing an empty
directory.
dist --index x-y works like --index 0 (same with annotate --index x-y) 
and should probably produce an error.

I have a neat table with the --index behaviour for several commands 
including exit codes if somebody is interested.

1 patch for repository http://darcs.net/screened:

Tue Jan 24 21:03:13 CET 2012  andreas.brandt.de@googlemail.com
  * Resolve issue2116: darcs dist --index no longer fails

Attachments

• resolve-issue2116_-darcs-dist-__index-no-longer-fails.dpatch
• unnamed

This patch bundle (with 1 patches) was just applied to the repository http://darcs.net/screened.
This message was brought to you by DarcsWatch
http://darcswatch.nomeata.de/repo_http:__darcs.net_screened.html#bundle-c38461503b67e6a7aadb2244f9789d77d36605a5

It might be worth moving the "darcs dist --index 1" test in tests/failing-
index-argument.sh out of the "failing tests" section.  This patch makes 
that part of the test succeed.

As mentioned in msg15057, dist --index behaves differently than other --
index options.  I think it's worth describing the behavior in dist --help 
so that users are aware of the differences.

I think the documentation is reason enough to hold off on accepting the 
patch just yet.  Committers, please correct me if I'm wrong or chose the 
wrong patch status.

This patch bundle (with 1 patches) was just applied to the repository http://darcs.net/reviewed.
This message was brought to you by DarcsWatch
http://darcswatch.nomeata.de/repo_http:__darcs.net_reviewed.html#bundle-c38461503b67e6a7aadb2244f9789d77d36605a5