On Tue, 17 Oct 2006 10:05:41 -0400 Aaron Bentley <aaron.bentley@utoronto.ca> wrote:Well his point was that they have pulled from each other directly or indirectly. You can safely say that rev 00aabbcc.. in _any_ repository is the same rev. This discussion started because of doubt expressed by some here on the list that the "simple" numbering scheme used by bzr can offer the same guarantee. That is, rev 1.2.1 may be completely different commits in different repos in bazaar. Just in case it wasn't clear, this is drop dead easy in Git too. Why? Uncommitted changes shouldn't be propagated. Once you have cloned the repo, you can checkout your own copy of the working tree files. Sean - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| James Bottomley | Re: Announce: Linux-next (Or Andrew's dream :-)) |
| Michal Piotrowski | Re: 2.6.21-rc5-mm4 |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
| Lovich, Vitali | RE: [PATCH] Packet socket: mmapped IO: PACKET_TX_RING |
git: | |
