On Thu, Apr 10, 2008 at 8:08 AM, Jean-Christian de Rivaz <jc@xxxxxxxx> wrote: > A possible way it to, by default, make git print the full form of the > command when a short form is used. So the user see the concept without > having to read the documentation and learn it gradually. I personally like > tools that act this way. It permit to make a basic and easy tutorial with > short commands that let know the general concept and show the full potential > of the tool. I think this would be a very nice solution, not only do you allow the user to realize what it is they are doing, you also provide them with an easy way to be more verbose. Perhaps they wish to switch from the default short behavior to a somewhat different form (e.g., change a default 'master' argument to another branch). When writing out the full form each time the user gets an intuitive and gradual introduction into the rest of git, without limiting them or more advanced users. > A "short form" flag in a user (not repository) configuration file should > allow to suppress the long form printout for the comfort of the users that > don't want it. Or perhaps, as I mentioned in the thread on "friendly refspecs", a "newbie" config option or command that turns on the informative verboseness options. As such, perhaps a "long form" flag would be more desired instead, to prevent existing developers from being spammed with information they do not are interested in. Cheers, Sverre Rabbelier -- 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
