New to Hg - best practices?
Isaac Jurado
diptongo at gmail.com
Wed Nov 5 23:54:59 UTC 2008
On Wed, Nov 5, 2008 at 11:11 AM, Marcos Scriven <marcos at scriven.org> wrote:
>
> 1) I get that I should (could) have one 'in' repo clone, one 'out'
> repo clone, and one or more working clones. What I'm not sure is
> how to integrate that with an IDE?
That depends on the IDE's Mercurial support.
> Do I effectively need a separate IDE project for each working set?
> Do I have to blow away that project when I've finished with that
> working set?
Probably yes, but, again, it depends on the IDE support. I don't use
IDEs very often, but considering the __initial__ paradigm of "one clone,
one branch" it seems that you would need a separate project (as it's a
separate repository).
> 2) I know it's best to get away from having a central repo, but
> presumably one does still need at least one repo to be 'the' repo,
> or master so to speak? How do you guys manage this?
As my memory is weak and my Internet "connectivity" is bad. I try to
take as much profit as possible of a cheap hosting I have. There I save
my "master" repositories either I work alone or collaborating (then my
colleagues have a symmetric setup)
> I understand you could have one repo for different versions of a
> piece of software, but not sure what's the best way to handle this.
Take Mercurial itself as an example:
http://www.selenic.com/mercurial/wiki/index.cgi/MercurialDevelopmentProcess
Four "main" repositories: hg, hg-stable, crew, crew-stable. The wiki
does not mention the details but I believe there is a heavy use of patch
queues; they can be quite sophisticated and handy if you get to
understand them well.
> 'I have cloned the source for server version x, now give me a clone of
> the client compatible with this'
Mmmm, a README file? I know that automation is an implicit goal of
computer programming, but that feels like it is trying to push it too
far.
Cheers.
--
Isaac Jurado Peinado
http://www.krenel.net
"The noblest pleasure is the joy of understanding"
Leonardo da Vinci
More information about the Mercurial
mailing list