Re: Remote branches and better documentation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 9/10/07, Steven Grimm <koreth@xxxxxxxxxxxxx> wrote:
> Joel Becker wrote:
> >       The suggestions are pretty simple.  First, when behavior is
> > changed invisibly (as the remote branch stuff was), can we note it in
> > the documentation?  I don't mean the ChangeLog, I mean the manpage.
>
> Please, no. I understand where you're coming from with this request, but
> think of it from the point of view of non-long-time users (or users who
> have been keeping up with the changelog) who want to look up some piece
> of information. The last thing they want to have to do is read through a
> bunch of irrelevant information related to the behavior of obsolete
> versions of git they've never even used.
>

Something that might be fun on the documentation on git web site is to
do something similar to git blame on the docs.  Each section (whatever
a section turns out to be) would have a "since x.y.z" link on it which
you could click and get older versions of the docs for people running
older builds.

Just a thought.
-Govind
-
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

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux