Re: Why is it bad to rewind a branch that has already been pushed out?

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

 



On Saturday 2007, February 03 19:42, Junio C Hamano wrote:

> Actually, if you are assuming a, h, and j are unrelated, then
> the merge done by Alice will _not_ revert 'j', so the history
> will perfectly be fine.  The merge result will have a half-baked
> work done with 'j', and everybody can build on top of.

Absolutely true.

Your point is a strong one.  I think I'm still not thinking big enough 
with the distributed development concept.  Your point has made me 
consider that I've been overly concerned about not rebasing pushed 
commits.  Provided you're willing to correct conflicts in a merge; they 
aren't as bad as I initially thought - in fact they offer a further 
choice when creating project history.

Thanks Junio.



Andy
-- 
Dr Andrew Parkins, M Eng (Hons), AMIEE
andyparkins@xxxxxxxxx
-
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]