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

From: Thomas Rast <trast@student.ethz.ch>
Date: Aug 2, 2010, 12:34 UTC
Message-ID: <201008021434.13748.trast@student.ethz.ch>
In-Reply-To: <7vbp9lprcs.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:

Show 12 quoted lines

> Jonathan Nieder <jrnieder@gmail.com> 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