Problems with hg push over SSH

Imbeault, Jean-Christian jeanchristian.imbeault at lehman.com
Tue Aug 28 20:33:11 CDT 2007


>From: mercurial-bounces at selenic.com
[mailto:mercurial-bounces at selenic.com] On Behalf Of Paul Sargent
>
>I think a reason that this comes up is that often people are replacing
centralised systems. Mercurial can do this, but the examples are written
with developers 'pulling' from each other, rather than all 'pushing'
back to a central (unmanned) repository. It's subtly different and I've
yet to see an example for it that shows the normal workflow.  

Exactly. I've read what I could but couldn't get my head around a
workflow that is distributed. I mean, how does it work? The only way for
me to pull in changes is to know everyone?

Some questions I have about the distributed model:

1- How does one get a copy including *all* the changes?
2- Or the newest version? The only way I could see this being possible
is by having a central repo where changes are checked into once in a
while.
3- How do I pull in changes when I don't know everyone who is working on
the project?
4- When I'm done, where do I push to?

I'm sure that the distributed model works well, it's just that I don't
understand it and from the small amount of documentation I've read I
haven't found a good description of how to use it. Does anyone have any
pointers?

Jc
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -

This message is intended only for the personal and confidential use of the designated recipient(s) named above.  If you are not the intended recipient of this message you are hereby notified that any review, dissemination, distribution or copying of this message is strictly prohibited.  This communication is for information purposes only and should not be regarded as an offer to sell or as a solicitation of an offer to buy any financial product, an official confirmation of any transaction, or as an official statement of Lehman Brothers.  Email transmission cannot be guaranteed to be secure or error-free.  Therefore, we do not represent that this information is complete or accurate and it should not be relied upon as such.  All information is subject to change without notice.






More information about the Mercurial mailing list