Johan Herland <johan@xxxxxxxxxxx> writes: > The new --max-commit-count option behaves similarly to --max-object-count, Hmm? Do we have --max-object-count at this point in the series, or am I missing a patch? > diff --git a/Documentation/git-pack-objects.txt b/Documentation/git-pack-objects.txt > index 20c8551..e43904e 100644 > --- a/Documentation/git-pack-objects.txt > +++ b/Documentation/git-pack-objects.txt > @@ -113,6 +113,14 @@ base-name:: > The default is unlimited, unless the config variable > `pack.packSizeLimit` is set. > > +--max-commit-count=<n>:: > + This option is only useful together with --stdout. > + Specifies the maximum number of commits allowed in the created > + pack. If the number of commits would exceed the given limit, > + pack-objects will fail with an error message. > + The number can be suffixed with "k", "m", or "g". > + The default is unlimited. It feels a tad funny to count number of commits in increments of 2^10, but that's Ok ;-). The patch itself looks fine. Thanks. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html