Junio C Hamano <gitster@xxxxxxxxx> writes: > [Stalled] > > * jh/receive-count-limit (2011-05-23) 10 commits > - receive-pack: Allow server to refuse pushes with too many objects > - pack-objects: Estimate pack size; abort early if pack size limit is exceeded > - send-pack/receive-pack: Allow server to refuse pushing too large packs > - pack-objects: Allow --max-pack-size to be used together with --stdout > - send-pack/receive-pack: Allow server to refuse pushes with too many commits > - pack-objects: Teach new option --max-commit-count, limiting #commits in pack > - receive-pack: Prepare for addition of the new 'limit-*' family of capabilities > - Tighten rules for matching server capabilities in server_supports() > - send-pack: Attempt to retrieve remote status even if pack-objects fails > - Update technical docs to reflect side-band-64k capability in receive-pack > > Would need another round to separate per-pack and per-session limits. What's the plan for this topic? I could keep it and list it among the 1.7.8 short-term goals once 1.7.7 ships, or I could drop it. It is not urgent as we just went into feature freeze for 1.7.7 but please start thinking about it. 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