git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
	Jonathan Nieder <jrnieder@gmail.com>,
	git@vger.kernel.org, bebarino@gmail.com, srabbelier@gmail.com,
	Thomas Rast <trast@student.ethz.ch>,
	Jakub Narebski <jnareb@gmail.com>,
	Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [RFC/PATCH 0/2] Documentation: kicking the "reset --hard" habit
Date: Mon, 1 Nov 2010 16:03:33 -0400	[thread overview]
Message-ID: <20101101200333.GG2340@fieldses.org> (raw)
In-Reply-To: <AANLkTiknyZBeWY8Z14EF+uq_2feJxJniVBwpwjUHgdEF@mail.gmail.com>

On Sun, Oct 31, 2010 at 05:25:20PM +0000, Ævar Arnfjörð Bjarmason wrote:
> On Sat, Oct 30, 2010 at 01:55, Matthieu Moy
> <Matthieu.Moy@grenoble-inp.fr> wrote:
> 
> >> Sadly, at least the user manual change suggested below is probably
> >> not suitable, since reset --keep and --merge have not been around
> >> since git 1.5.3 days.  Ideas for working around that and other
> >> comments would be welcome.
> >
> > Do we really want to keep the user manual compatible with 1.5.3
> > forever? It's nice to keep the user manual usable by slightly outdated
> > Gits, but 1.5.3 starts being really old, and older docs are still
> > available on the web (like
> > http://www.kernel.org/pub/software/scm/git/docs/v1.5.3.8/git.html ).
> 
> I didn't know we even did this with our user manual. When I read
> manuals for version X (e.g. PostgreSQL, Emacs or libc versions) I
> fully expect the features described to only work on the documented
> version unless otherwise noted.

Yeah, previous versions of the user manual are still around if people
need them.  For a book or an independent website a wider range of
versions would make more sense, but for documentation destributed with
the git source I think we can afford to be more aggressive.

If we think information about old versions is really important maybe
someone could find a way to incorporate it in a way that doesn't intrude
into the main text too much (e.g. footnotes or an appendix.)

--b.

      reply	other threads:[~2010-11-01 20:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-29  8:35 [RFC/PATCH 0/2] Documentation: kicking the "reset --hard" habit Jonathan Nieder
2010-10-29  8:38 ` [RFC/PATCH 1/2] Documentation: suggest "reset --merge" more often Jonathan Nieder
2010-11-03  9:32   ` Stephen Boyd
2010-10-29  8:39 ` [RFC/PATCH 2/2] Documentation: suggest "reset --keep" " Jonathan Nieder
2010-10-30  1:55 ` [RFC/PATCH 0/2] Documentation: kicking the "reset --hard" habit Matthieu Moy
2010-10-31  3:53   ` Junio C Hamano
2010-10-31 14:04     ` Matthieu Moy
2010-11-05 14:39       ` Oldest Currently Distributed Git {Re: [RFC/PATCH 0/2] Documentation: kicking the "reset --hard" habit} Drew Northup
2010-10-31 17:25   ` [RFC/PATCH 0/2] Documentation: kicking the "reset --hard" habit Ævar Arnfjörð Bjarmason
2010-11-01 20:03     ` J. Bruce Fields [this message]

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=20101101200333.GG2340@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=avarab@gmail.com \
    --cc=bebarino@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=jrnieder@gmail.com \
    --cc=srabbelier@gmail.com \
    --cc=trast@student.ethz.ch \
    /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).