On Sun, Jun 15, 2008 at 01:21:57PM -0700, Junio C Hamano wrote: > SZEDER Gábor <szeder@xxxxxxxxxx> writes: > > I think this patch is rather a bugfix in the user interface than a new > > feature. > > Strictly speaking, this is a new feature but I think the documentation > value to clarify -u stands for "update" is great enough to make it an > exception. Well, my reasoning was that every short option must have a long equivalent, therefore the lack of long options is a bug (even if this does not lead to e.g. a runtime error). > I've rewritten (from empty! Szeder, next time please write > sensible commit log message to defend your changes, instead of having _me_ > to defend your changes to others here, like this) the commit log message > to clarify this point. Sorry, I though the rationale behind the changes (i.e. "why?") is trivial even from that one-liner: add long options, because, well, they do not exist. In fact, I considered to write something like "these long options are '--update' and '--force'" in the commit message. But I dropped it, because that explained _what_ the patch does, and I understood that that should not go into the commit message. Anyway, I will take care next time. Regards, Gábor -- 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
