On Tue, Sep 11, 2007 at 12:32:28AM +0700, Nguyen Thai Ngoc Duy wrote: > On 9/11/07, Carlos Rica <jasampler@xxxxxxxxx> wrote: > > 2007/9/10, Nguyen Thai Ngoc Duy <pclouds@xxxxxxxxx>: > > > I have come to this post: > > > > > > http://mail.gnome.org/archives/foundation-list/2007-September/msg00043.html > > > > > > and I agree with him that git-push description from git-help is not > > > very intuitive. Can we change it to something easier to understand? > > > Technically correct descriptions can always live in man pages. How > > > about "Push/Update branches/tags into remote repository"? (not really > > > good imo) > > > > Now that you have seen this issue, a better way of suggesting it > > is composing a patch and sending it to the mailing list, following > > the recommendations in the file: Documentation/SubmittingPatches. > > Then it will be discussed and eventually accepted. This way, everybody > > will invest the minimum time required for such a change. > > > > Ok. I didn't look at the code when suggesting such a change. It > requires more work than just a string change (that I thought). I'll > take it back. Well, I think it'd be a reasonable project to take a look at the output from "git" and see what we could do to make it easier to understand. It may of course be impossible to find a single one-line description of every common git command that is a) 60 charactes or less, b) readable with *no* git-specific prerequisites and c) technically accurate. But maybe we could get a little closer. An extremely brief (3-4 line) glossary at the beginning might help. If push comes to shove, we could also replace the automatic generation of those summaries if hand-tailored descriptions would work better, as long as it doesn't look like it'll lead to bit-rot. --b. - 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
