[Chandler-dev] Commits message size limits

[Heikki Toivonen]

Currently large commits (500k?) will end up in a queue that will need
manual handling. Typically bear has approved them all for trunk, but has
deleted some branch commit messages. Yesterday a large trunk commit got
deleted, which came as a big surprise at least to me.

I would like us to set a policy so that we can avoid surprises in the
future.

My recommendation is to never delete any trunk commits messages.

As for branches, I can see situations where a relatively old branch is
brought up to date, which can result in a huge commit message without
much value. Therefore I think it would be ok to delete large
merge-from-trunk messages. I think I would like to raise the limit to
something like 1 MB, though.

-- 
  Heikki Toivonen


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 252 bytes
Desc: OpenPGP digital signature
Url : http://lists.osafoundation.org/pipermail/chandler-dev/attachments/20071101/ff7ed633/signature.pgp