"project" or "subproject" or "module" or "component" or ... whatever. :-)
/dev/mrg
On 1/19/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
Sounds ok. If there are no other suggestions till Sunday, I'll use
"unpublished".
Andrus
On Jan 19, 2007, at 7:41 PM, Mike Kienenberger wrote:
> How ab
Sounds ok. If there are no other suggestions till Sunday, I'll use
"unpublished".
Andrus
On Jan 19, 2007, at 7:41 PM, Mike Kienenberger wrote:
How about unpublished instead of private?
On 1/19/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
On Jan 19, 2007, at 7:16 PM, Michael Gentry wro
How about unpublished instead of private?
On 1/19/07, Andrus Adamchik <[EMAIL PROTECTED]> wrote:
On Jan 19, 2007, at 7:16 PM, Michael Gentry wrote:
> Seems fairly logical, but Subversion allows us to move things around
> if it needs to be changed again.
True, just trying not to do it too oft
On Jan 19, 2007, at 7:16 PM, Michael Gentry wrote:
Seems fairly logical, but Subversion allows us to move things around
if it needs to be changed again.
True, just trying not to do it too often to avoid upsetting local
Eclipse workspaces.
I am a little confused by the "private" in the n
Seems fairly logical, but Subversion allows us to move things around
if it needs to be changed again.
I am a little confused by the "private" in the names, though. Maybe I
just don't understand what you were trying to do, but the term seems
to imply non-open source to me, which of course is not
We have a new TLP repo created for us:
https://svn.apache.org/repos/asf/cayenne/
Since repo migration will require everybody to re-import stuff in
Eclipse, I figured it is a good time to move a few other things
around. So here is the plan. If we can reach lazy consensus, I can
move the cod
