From: "Stefano Spinucci" <virgo977virgo@gmail.com>
To: git@vger.kernel.org
Subject: Re: git docs on kernel.org too new?
Date: Thu, 1 Feb 2007 19:14:26 +0100 [thread overview]
Message-ID: <906f26060702011014r254ffd5frd75296c8443078ab@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.62.0702011051300.31498@torch.nrlssc.navy.mil>
this isn't the first time someone is confused by git docs, and I guess
why we can't have a documentation page as
http://www.python.org/doc/versions/
---
Stefano Spinucci
next prev parent reply other threads:[~2007-02-01 18:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-01 17:26 git docs on kernel.org too new? Brandon Casey
2007-02-01 18:14 ` Stefano Spinucci [this message]
2007-02-01 19:20 ` Shawn O. Pearce
2007-02-01 19:17 ` Shawn O. Pearce
2007-02-01 19:21 ` Brandon Casey
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=906f26060702011014r254ffd5frd75296c8443078ab@mail.gmail.com \
--to=virgo977virgo@gmail.com \
--cc=git@vger.kernel.org \
/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).