One other solution I just thought of is we could move CHANGES.txt to
the docs directory and during packaging, copy it up to the top level.
The upside to this is contrib committers would have the ability to
commit to it, the downside is it isn't immediately obvious to casual
viewers of the source code.
Thoughts?
-Grant
On Jun 27, 2008, at 1:02 PM, Karl Wettin wrote:
Yeah, I saw the response there. Should it be a single changes for
contrib, or one per contrib module?
karl
27 jun 2008 kl. 00.46 skrev Grant Ingersoll:
One alternative, in the short term, is to keep a CHANGES on a per
contrib basis... I realize that is less than ideal. I've asked on
infra
On Jun 26, 2008, at 3:43 PM, Grant Ingersoll wrote:
Hmmm, true... Let me see if we can do per file karma.
-Grant
On Jun 26, 2008, at 1:03 PM, Karl Wettin wrote:
Contrib committers does not seem to have karma to trunk/
CHANGES.txt.
karl
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
