I meant "accessible to Derby contributors" not "acceptable to Derby
contributors."
David Van Couvering wrote:
Yes, well, that would work except that
(a) This is not acceptable to Derby contributors who are not committers,
and I'd like their help, we have a lot to do before we cut our release
branch next week
(b) I don't feel comfortable making changes that are somewhat specific
to Derby in that location, although I suppose I could make a
derby-specific derivative. But item (a) is more to the point...
David
Paul Querna wrote:
David Van Couvering wrote:
Hi, all. I want to grab a copy of the Perl scripts for updating the
license header and put them (temporarily) into the Derby code tree so
those of us in Derby can collaborate, including making Derby-specific
changes.
Is this a problem for anyone? Is there a certain way I should (or
should not) do this?
How about the committers repository, rather than Derby:
https://svn.apache.org/repos/private/committers/tools/
-Paul
---------------------------------------------------------------------
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]