[PATCH 2 of 4] clone to master bookmark if available

Victor Suba vosuba at gmail.com
Fri Nov 11 02:30:14 CST 2011


Hi Arne,

>> Git will fetch everything unless you explicitly tell it to fetch only a
>> specific branch,
>> so there's no risk of not having every branch from the remote when you go
>> offline.

> So what you meant is that you don’t want multistep pulling?
> If I don’t pull the head explicitely, the next who pulls from me does not
get
> it?

Right, I mean I don't think you have to explicitly pull each head if there
is a mechanism
for specifying what should be automatic and what not, but think it is
beneficial to have
control over change propagation.  I don't want to be responsible for
everything I might
pull from someone else - especially since in base Hg deleting history is
not default behavior.

If I pull everything I'm liable to get something broken that I don't even
care about and
will never test, then I might inadvertently push that upstream or someone
else pull from me.

Or, I pull a fork from someone else, test it and find out that it doesn't
work so I
don't want to merge it with my head, but now "hg push" will moan at me for
pushing multiple new heads - my resolution is I have to use "hg push rev"
explicitly
from now until the fork is fixed - which means waiting for the originator
to fix it or
pulling the knife out ("strip").

Cheers,
Vic

On Thu, Nov 10, 2011 at 10:23 PM, Arne Babenhauserheide <arne_bab at web.de>wrote:

> Am Donnerstag, 10. November 2011, 16:15:35 schrieb Victor Suba:
> > Git will fetch everything unless you explicitly tell it to fetch only a
> > specific branch,
> > so there's no risk of not having every branch from the remote when you go
> > offline.
>
> So what you meant is that you don’t want multistep pulling?
> If I don’t pull the head explicitely, the next who pulls from me does not
> get
> it?
>
> (trying to understand your post)
>
> Best wishes,
> Arne
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20111111/49731d1e/attachment.html>


More information about the Mercurial-devel mailing list