Re: Dangers of working on a tracking branch

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Thursday, February 15, 2007 at 17:09:18 (-0500) Shawn O. Pearce writes:
>...
>Lets say you patch git-clone to create these branches under
>refs/heads, and also under refs/remotes/origin.  Now someone else
>modifies one of those branches, and you do a git-fetch to get the
>latest.  The tracking branch under refs/remotes/origin would update,
>but not the one in refs/heads.  Which means "jumping right in" may
>actually cost you a lot more time, because you are now starting on
>something that is several days old.

Granted, but this would be the same as creating the branch by hand,
then going rock-climbing over the weekend, while my colleagues toiled,
and coming back on Monday to find 15 checkins on that branch, right?

At which point I could .... rebase?  Do a pull?


Bill
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]