Newbie Configuration Question

[chowarmaan at gmail.com]

Thanks. I saw things that included the hg serve, and some concerns from  
some people in what I was reading about many projects off of the same main  
folder (S:\). We have a number of different projects and some maintenance  
(in the field, limited change) versions all in the same tree.

On Jul 2, 2010 4:31pm, Daniel Carrera <dcarrera at gmail.com> wrote:
> Hello Steven,



> Unless I am missing something, what you want is very easy with

> Mercurial. I am not a Windows user so I might have some details wrong,

> but basically:



> 1) Create repository in shared drive:



> hg init S:\Project1



> (add project files)



> 2) Developer clones the project.



> hg clone S:\Project1 D:\Project1 (for example)



> 3) Developer A makes changes and wants to contribute them back:



> hg push S:\Project1



> 4) Developer B wants to grab all the latest work from the shared drive:



> hg pull S:\Project1

> hg merge (merge work with mine)

> hg push (send the merged stuff back to the shared drive)





> Am I missing something? Looks like a very standard setup.





> On Fri, Jul 2, 2010 at 10:07 PM, Steven Scott chowarmaan at gmail.com> wrote:

> > I am new to Mercurial, and am evaluating if it will work for our  
> development

> > team. We are a Windows shop coming from Visual SourceSafe, and are

> > considering switching to Mercurial. It looks like it will do what we  
> need,

> > but I have a couple requirements from the powers that be that I am not  
> sure

> > how to configure.

> >

> > I need a central repository on a shared drive (S:\ for instance) for  
> all our

> > projects (S:\Project1, S:\Project2, etc...). Also, each developer will

> > clone from this central repository when they do their work and then

> > contribute back. The central drive is also for backups for code escrow

> > which we need to do with some customers.

> >

> > My question is, can this be done? What is the best way to do it, and  
> how do

> > I do it in the Windows version of Mercurial? We are looking at using

> > version 1.6.

> >

> >

> >

> > _______________________________________________

> > Mercurial mailing list

> > Mercurial at selenic.com

> > http://selenic.com/mailman/listinfo/mercurial

> >

> >







> --

> No trees were killed in the generation of this message. A large number

> of electrons were, however, severely inconvenienced.

> _______________________________________________

> Mercurial mailing list

> Mercurial at selenic.com

> http://selenic.com/mailman/listinfo/mercurial

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20100702/1e4da299/attachment.html>