Linus Torvalds <torvalds@linux-foundation.org> writes:Yes, I know. But when looking at the history with gitk, it feels quite intuitive to just get rid of the one new commit that appeared on top of the "good" history. Without that kind of visualisation I would surely always just use ORIG_HEAD as a reference. Perhaps gitk could (optionally) also show ORIG_HEAD. That way we could just do gitk --all after a pull and see what got pulled, and everything else was already there, too, if needed. - 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
| Linus Torvalds | Linux 2.6.27-rc8 |
| Greg KH | [GIT PATCH] driver core patches against 2.6.24 |
| Linus Torvalds | Linux 2.6.20-rc6 |
| Mike Snitzer | Re: Distributed storage. |
git: | |
| Gerrit Renker | [PATCH 03/37] dccp: List management for new feature negotiation |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | [GIT]: Networking |
| Herbert Xu | Re: Kernel oops with 2.6.26, padlock and ipsec: probably problem with fpu state ch... |
