Yes I'm interested in trying the git once that place is ready.

--wei

On Mon, Feb 23, 2009 at 3:48 PM, James Dixson <[email protected]> wrote:

> Ok. I made a request of INFRA, we should have capability in a couple of
> days. I will put some instructions together in the meantime.
>
> --
> James
>
>
>
> On 2/23/09 3:34 PM, "Scott Comer (sccomer)" <[email protected]> wrote:
>
> > yes, i'm working with manoj and wei to get some etch services granted
> > and then continue
> > development. but they are not committers yet and we could use this to
> > work on them.
> >
> > i could use it for my own work, too.
> >
> > scott out
> >
> > James Dixson wrote:
> >> I personally have been moving all of my day-to-day development from
> >> subversion to git (http://git-scm/com).  I find it much easier to
> >> manage multiple branches of development and experiment and try other
> >> folks patches.
> >>
> >> I have noticed recently that the infrastructure team has been
> >> experimenting with GIT mirrors of apache subversion projects.
> >>
> >> The purpose of the git mirror would be two fold:
> >>  1. To have a pre-cloned GIT repository for Etch
> >>  2. To allow other public GIT repos to reference the mirrored repository
> >>
> >> #2 would be particularly helpful for folks out there experimenting
> >> with Etch bindings/transports or potential new Etch core services
> >> (like Etch Router) to do publicize their work more readily, (IMHO of
> >> course :-) )
> >>
> >> Is there anyone else besides myself that would be interested in a
> >> public git mirror of the etch repository? Are there any objections to
> >> requesting a GIT mirror from the infrastructure team?
> >>
> >> NOTE: subversion is still the final source of truth, if it is not
> >> accepted/checked-in to the subversion tree is not yet part of the
> >> official etch codebase.
> >>
> >> thoughts?
> >>
> >> --
> >> james
> >>
>
> --
> James Dixson
> Manager, Software Development
> CUAE Engineering, Cisco Systems
> (e) [email protected]
> (p) 512-336-3305
> (m) 512-968-2116
>
>
>

Reply via email to