Issue 1369 get/pull --max-count

Title get/pull --max-count
Priority feature Status needs-implementation
Milestone Resolved in
Superseder Nosy List darcs-devel, dmitry.kurochkin, ganesh, gh, jaredj, kowey, thorkilnaur, zooko
Assigned To
Topics Matchers, ProbablyEasy

Created on 2009-02-24.11:36:29 by ganesh, last changed 2010-11-30.08:13:00 by gh.

msg7350 (view) Author: ganesh Date: 2009-02-24.11:36:26
I would like a --count argument to pull (and perhaps any other interactive
command). This would be mainly useful when tracking down failures using binary
chop or batches.
msg7353 (view) Author: kowey Date: 2009-02-24.11:55:21
Marking ProbablyEasy.  Note that changes --count already exists, if anybody
wants to work on this.  Sounds like a good starter task for a darcs sprint.
msg8376 (view) Author: kowey Date: 2009-08-23.09:48:57
Merging issue1501 in (which also wants get --count).

One thing I didn't understand when I first replied in msg7353 is that changes
--count does something different (it outputs the number of patches).

I guess we could call this --max-count instead, which seems like it'd be
consistent with changes --max-count
Date User Action Args
2009-02-24 11:36:29ganeshcreate
2009-02-24 11:55:25koweysettopic: + ProbablyEasy
nosy: + jaredj
status: unread -> unknown
messages: + msg7353
2009-08-23 09:44:04koweylinkissue1501 superseder
2009-08-23 09:49:03koweysetstatus: unknown -> needs-implementation
nosy: + zooko
topic: + Matchers
messages: + msg8376
title: pull --count -> get/pull --max-count
2009-08-25 17:41:17adminsetnosy: + darcs-devel, - simon
2009-08-27 14:30:08adminsetnosy: kowey, darcs-devel, zooko, ganesh, thorkilnaur, jaredj, dmitry.kurochkin
2010-11-30 08:13:00ghsetnosy: + gh