From: Thomas Rast <trast@student.ethz.ch>
To: Junio C Hamano <gitster@pobox.com>
Cc: "Jonathan Nieder" <jrnieder@gmail.com>,
git@vger.kernel.org, "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
"Geoff Russell" <geoffrey.russell@gmail.com>
Subject: Re: [PATCH/RFC v2] Documentation: flesh out “git pull” description
Date: Mon, 2 Aug 2010 14:34:13 +0200 [thread overview]
Message-ID: <201008021434.13748.trast@student.ethz.ch> (raw)
In-Reply-To: <7vbp9lprcs.fsf@alter.siamese.dyndns.org>
Junio C Hamano wrote:
> 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
next prev parent reply other threads:[~2010-08-02 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-01 2:54 [PATCH/RFC v2] Documentation: flesh out “git pull” description Jonathan Nieder
2010-08-01 3:03 ` [PATCH/RFC v2 resend] " Jonathan Nieder
2010-08-02 4:32 ` [PATCH/RFC v2] " Junio C Hamano
2010-08-02 12:34 ` Thomas Rast [this message]
2010-08-02 13:30 ` Junio C Hamano
2010-08-02 21:39 ` [PATCH] " Jonathan Nieder
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201008021434.13748.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=avarab@gmail.com \
--cc=geoffrey.russell@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jrnieder@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).