Hi, On Tue, 28 Nov 2006, Carl Worth wrote: > On Sat, 25 Nov 2006 02:12:38 -0800, Junio C Hamano wrote: > > * The new "--depth $n" parameter to git clone/fetch tries to > > limit the commit ancestry depth to $n. > [...] > Has though been given to make the depth selection consistent with > other limiting options for rev-parse and rev-list? For example, I'd > like to be able to use --since to get a shallow clone, (so should > --depth instead be --max-count?, and can we re-use some existing > machinery here?). I briefly considered that, but decided against it, for two reasons: 1) it puts the burden of calculation on the server, and 2) I was not at all sure if the whole shallow stuff would be useful to begin with (and therefore avoided complicated stuff as much as possible). > > Petr Baudis (1): > > Make git-clone --use-separate-remote the default > ... > > Junio C Hamano (19): > > git-merge: make it usable as the first class UI > > Also very exciting. Please do keep up the user-interface improvements, > everybody. I concur. 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