On Tuesday 2006, November 28 19:11, Nicholas Allen wrote:You want to tell git about a rename that will never fail to be detected? No problem. $ git mv oldname newname $ git commit The corner cases you speak about are when you rename and edit. For me, I prefer that to be detected as at least the detection algorithm can be tuned - there is no fixing it if the VCS was forced to consider it a rename. When I started using git I was worried about the lack of a rename, but now I realise that it's not needed - it's pointless. The VCS is snapshotting moments in time, that's it. Then by making cleverer and cleverer interpreters of those snapshots you have the potential to do stuff that is far more useful than "just" rename recording. Andy -- Dr Andrew Parkins, M Eng (Hons), AMIEE andyparkins@gmail.com - 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
| Jeff Chua | 2.6.27rc1 cannot boot more than 8CPUs |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Winkler, Tomas | RE: iwlwifi: fix build bug in "iwlwifi: fix LED stall" |
| Evgeniy Polyakov | Re: [BUG] New Kernel Bugs |
git: | |
| David Miller | [GIT]: Networking |
| Gerrit Renker | [PATCH 15/37] dccp: Set per-connection CCIDs via socket options |
| Andrew Dickinson | tx queue hashing hot-spots and poor performance (multiq, ixgbe) |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
