Strategies for push/merge problem?

[Arne Babenhauserheide]

Am Sonntag 20 Juli 2008 23:22:36 schrieb Alpár Jüttner:
> For example people can exchange changesets directly and every team can
> have an own "sub-main" repo, where they collects their (somewhat review)
> commits and which is regularly pulled by a maintainer of a "more main"
> repo.

Or they can push it from that repo to a main repo. 

So I'd like to ask: What is this discussion about? 

Is it about how to help someone to use Mercurial in his environment, or is it 
about "how Mercurial should be used"? 

Differently put: Is it "you can use hg in your envorinment like this", 
or "adapt your environment. You're not making the most out of hg"? 

> > In my experience, no one 'owns' a particular repo.  No one gates any
> > pushing to a repo.  To do so in my corporate environment is a disaster
> > when you attempt to scale.
>
> Probably yes, assuming that you attempt to do the whole process of
> managing the source code exactly in the same way as you did it with
> CVS/SVN.

Since companies are often slower to adapt: That's quite possible, and given 
the human nature I know, it is also reasonable. 

Get the power of Mercurial without throwing away most of the familiarity of 
cvs/svn. 

Sounds like a quite reasonable plan to me. 

Best wishes, 
Arne
-- 
-- Weblog: http://blog.draketo.de
-- Infinite Hands: http://infinite-hands.draketo.de - singing a part of the 
history of free software. 
-- Ein Würfel System: http://1w6.org - einfach saubere (Rollenspiel-) Regeln

-- PGP/GnuPG: http://draketo.de/inhalt/ich/pubkey.txt
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
Url : http://selenic.com/pipermail/mercurial/attachments/20080721/0dac975b/attachment.pgp