(Sorry for the repeat; my mail client tried to send this as HTML at first and the git list rejected it.) On 19/10/2007, Jeff King <peff@peff.net> wrote: > This makes the fetch output much more terse. It is likely to > be very controversial. Here's an example of the new output: > > Indexing objects: 100% (1061/1061), done. > Resolving deltas: 100% (638/638), done. Those two lines are actually my beef with the fetch output. As a newbie, I had no idea what "Indexing objects" actually meant. We have this thing called "the index" in git so I would expect "Indexing objects" to have something to do with that, but it doesn't seem to. How about something more descriptive of the high-level operation that's going on, along the lines of: Gathering changes from remote: 100% (1061/1061), done. Applying changes locally: 100% (638/638), done. -Steve - 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 | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Heiko Carstens | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Tony Lindgren | [PATCH 37/90] ARM: OMAP: MPUIO wake updates |
| Greg Kroah-Hartman | [PATCH 001/196] Chinese: Add the known_regression URI to the HOWTO |
git: | |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Benjamin Herrenschmidt | Re: powerpc allmodconfig |
