Thanks for the informative response. It helped but I'm still slightly confused by git - I think I need to play around with it a bit more to understand and get more familiar with the concepts... Purely from an initial usage point of view though, for me at least, the bzr output needed no explanation which I think is indicative of a good user interface whereas the git was not so clear or obvious - there must be room for improvement in git's user friendliness here surely. But that might just be because I am clueless when it comes to the way git works and the concepts it uses ;-) Nick - 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
| Washington Odhiambo | Weird Problem with NAT - more details |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Andrew Morton | -mm merge plans for 2.6.23 |
git: | |
| Jarek Poplawski | [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Gerrit Renker | [PATCH 0/37] dccp: Feature negotiation - last call for comments |
| David Miller | Re: [GIT]: Networking |
| Denys Fedoryshchenko | thousands of classes, e1000 TX unit hang |
