Hi, On Wed, 13 Dec 2006, Andy Parkins wrote: > On Wednesday 2006, December 13 21:35, Junio C Hamano wrote: > > * git-revert should be called git-invert. It doesn't remove a change > from history, it simply applies another commit that does the > opposite of whatever commit you are "revert"ing. That's an inversion. No. An inversion is the _opposite_. Not an undo. Besides, The fact that revert _adds_ to history is a nice way to document that you reverted that change. And you can even explain in the commit message, why you did it. > * git-fetch output is confusing: > remote: Generating pack... > remote: Done counting 189146 objects. > remote: Result has 186566 objects. > remote: Deltifying 186566 objects. > remote: 100% (186566/186566) done > Unpacking 186566 objects > 24% (44792/186566) done > Some questions from the point of view of a newbie: what is a pack? what is > an object? Why is the remote counting them? Which remote am I reading > from? What am I fetching? What is "Deltifying"? How much data do I have > to download (number of objects doesn't tell me). How long has this taken? > How long is left to go? IMHO it is better for a newbie to see that _something_ is happening. A newbie cannot, and does not want to, understand exactly what is going on. So, think of it as our response to Windows' non-progress-bar: when you start up Windows, there is a progress-bar, except that it does not show progress, but a Knight Rider like movement, only indicating that it does something. Ciao, Dscho - 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