Re: [PATCH/RFC v2] Documentation: flesh out “git pull” description

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

 



Junio C Hamano wrote:
> Jonathan Nieder <jrnieder@xxxxxxxxx> writes:
> 
> > Junio: ideally for this to work, git-pull.html would need to get the
> > same special treatment as git.html gets.  Does that seem doable?  Is
> > Meta/dodoc.sh still the script to do it?
> 
> I am a bit reluctant to see stalenotes[] being abused; that ugly hack is
> in effect _only_ while k.org documentation is being built to hang the "You
> are reading the latest dev version, newer than anything released" sign on
> the front door.
> 
> People with older git have documentation shipped with their versions, no?

The problem is that google invariably turns up the 'master' docs at
k.org when you look for a git commmand (and that we point people to
them all the time on #git).  Hence I suggested not outright removing
this safety warning from the docs that even people running 1.5.x will
read.

-- 
Thomas Rast
trast@{inf,student}.ethz.ch
--
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]