On Sun, Jan 25, 2009 at 02:58:34PM -0800, Keith Cascio wrote: > OK, point taken. I wasn't trying to be idiosyncratic at all. Just > trying to be explicit and avoid all confusion. Since all diff options > already have default values, primer looks to me like the layer one > step above defaults, hence the painting analogy. Mercurial calls it > "defaults", but that doesn't mean we should necessarily follow in > their footsteps (see > http://article.gmane.org/gmane.comp.version-control.git/107103). > > I think being as clear as possible about what primer is, that is it > NOT defaults, helps to feel more comfortable with its consequences, > i.e. in my opinion, that it will not break things. I'm not sure I agree that they are not new defaults, but any such argument is going to get into the exact definition of "default" which is not really useful to the task at hand. I think "options" is a better word (as in, pretend like you already specified these "options" on the command line), but I am not going to insist on that. I mainly just wanted to point out that I found "primer" confusing. Enough so that, even though I knew you were interested in this topic from your previous mails, I saw the word "primer" and said to myself: "what in the world is this patch about?" -Peff -- 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
