On Mon, Mar 23, 2009 at 2:00 AM, Junio C Hamano <gitster@xxxxxxxxx> wrote: > Felipe Contreras <felipe.contreras@xxxxxxxxx> writes: > >>> See this lengthy thread: >>> >>> http://article.gmane.org/gmane.comp.version-control.git/106634 >> >> I've obviously seen that thread because I started it. >> >> Can you write more than one line to explain your point? > > The "lengthy thread" look lengthier than necessary because it has a > more-or-less unrelated side topic ("where is $HOME on Windows"), but I > think the main point by WIncent is that onus lies on whoever repeats the > previous discussion to provide what is different in this round to convince > others to read the patch. For example, this > > http://article.gmane.org/gmane.comp.version-control.git/106657 > > was not answered by you in the previous round, and I do not think this > round is any different. Was I supposed to answer it? I am trying to address the points raised in those discussions in this patch series. > I personally find that between what Wincent presented in > > http://article.gmane.org/gmane.comp.version-control.git/106673 > > as "Something like either ... or ...", the first one that shows the actual > configuration file contents and then mention 'git config' a good enough > compromise. Except that in the previous patch[1] (#7) I'm adding a new global section that explains how to configure git in different ways: I don't think it makes sense to explain "either ... or ..." each time we deal with 'git config' in the manual if it's explained in the very beginning. [1] http://article.gmane.org/gmane.comp.version-control.git/114163 -- Felipe Contreras -- 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
