axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjiva Weerawarana" <sanj...@watson.ibm.com>
Subject Re: finalizing C++ -dev/-user list stuff
Date Tue, 25 Nov 2003 19:02:49 GMT
No, unfortunately not. There's apparently no way to do that without
having a totally separate repository.

Sorry ...

Sanjiva.

----- Original Message -----
From: "Tom Jordahl" <tomj@macromedia.com>
To: <axis-dev@ws.apache.org>
Sent: Tuesday, November 25, 2003 1:08 AM
Subject: RE: finalizing C++ -dev/-user list stuff


> Sanjiva,
>
> Would this allow me to get the Java CVS commit messages and NOT get the
C++ commit messages?
>
> That is what is important to me.
>
> --
> Tom Jordahl
> Macromedia Server Development
>
> -----Original Message-----
> From: Sanjiva Weerawarana [mailto:sanjiva@watson.ibm.com]
> Sent: Monday, November 24, 2003 12:49 AM
> To: axis-dev@ws.apache.org
> Subject: finalizing C++ -dev/-user list stuff
>
> I'd like to close this off. To be sort of consistent with Xerces
> and to follow the spirit of having java/, c/ etc. under ws-axis,
> I suggest we create a new axis-cvs list and post all commit messages
> to that list. Then we create separate axis-dev-c and axis-user-c
> lists for the C++ Axisers.
>
> I suggest all current members of axis-dev be made members of axis-cvs
> and that future members decide for themselves what they wish. This
> way the current folks see no change in behavior.
>
> Are current AXISers ok with this? If so let's get a vote and get it
> done with. If not what do you suggest doing - pls remember that we
> have room for other languages in the structure (java/, c/) and that
> there is precedent in a certain way.
>
> Sanjiva.
>
> ----- Original Message -----
> From: "Sam Ruby" <rubys@apache.org>
> To: <general@ws.apache.org>
> Cc: <pmc@ws.apache.org>; <axis-dev@ws.apache.org>
> Sent: Wednesday, November 12, 2003 4:14 AM
> Subject: Re: create separate CVS?
>
>
> > Sanjiva Weerawarana wrote:
> >
> > > I checked the Xerces situation and it looks like they have
> > > one repository and yet multiple mailing lists. Does anyone
> > > know what they do? I'd prefer to keep it consistent and
> > > mirror their model.
> > >
> > > Also, that was the whole point of having put a java/ dir
> > > under ws-axis/ for example.
> > >
> > > Sanjiva.
> >
> > There is a separate xerces-cvs mailing list, in addition to a -c-dev,
> > -j-dev, -j-user, and -p-dev mailing list.
> >
> > > ----- Original Message -----
> > > From: "Sanjiva Weerawarana" <sanjiva@opensource.lk>
> > > To: <pmc@ws.apache.org>; <axis-dev@xml.apache.org>
> > > Sent: Friday, November 07, 2003 9:24 PM
> > > Subject: create separate CVS? (was: Re: VOTE: move Axis/C++ to direct
> > > sub-project under WS PMC)
> > >
> > >
> > >
> > >>Hi Sam,
> > >>
> > >>
> > >>>Where should the cvs commit messages for ws-axis be directed?
> > >>
> > >>Good question.
> > >>
> > >>
> > >>>It would be trivial (read: I volunteer to do it) to clone the ws-axis
> > >>>cvs tree and prune the java branch from one copy and the c branch
from
> > >>>another.  Both branches would retain their original version history.
> > >>>
> > >>>What I would need to achive this would be a list of directories to
> > >>>retain/remove from each copy.
> > >>
> > >>The commit messages would definitely be a problem .. directing that
> > >>to the right list was a big part of creating new -dev lists. I
> > >>assume there's no way to have commit messages to one part of a
> > >>repository go to one address and the rest to another??
> > >>
> > >>What do people think of the idea of creating a separate CVS too?
> > >>The C++ version depends on the Java version for tooling, so that would
> > >>definitely be a bit of a pain.
> > >>
> > >>Sanjiva.
> > >>
> > >>
> > >>---------------------------------------------------------------------
> > >>To unsubscribe, e-mail: pmc-unsubscribe@ws.apache.org
> > >>For additional commands, e-mail: pmc-help@ws.apache.org
> > >>
> > >>
> > >
> > >
> >


Mime
View raw message