From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Steffen Prohaska <prohaska@zib.de>, git@vger.kernel.org
Subject: Re: [PATCH] WinGit: include html pages from official git.git's html branch
Date: Sun, 30 Sep 2007 00:23:59 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709300022080.28395@racer.site> (raw)
In-Reply-To: <7vr6khjf22.fsf@gitster.siamese.dyndns.org>
Hi,
On Sat, 29 Sep 2007, Junio C Hamano wrote:
> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>
> > On Sat, 29 Sep 2007, Steffen Prohaska wrote:
> >
> >> It is assumed that a matching version of the html documentation is
> >> available as the HEAD of /doc/git/html/.git. If not an error will be
> >> reported.
> >>
> >> This patch doesn't include a mechanism to fetch the html pages to
> >> /doc/git/html/.git. You should manually clone them. Maybe this could
> >> handled as a submodule of msysgit?
> >
> > I'd rather handle it as in git.git, as another branch, and not check
> > it out in /git/html/, but rather use "git read-tree
> > --prefix=/tmp/WinGit/share/git/html origin/html", or some such.
>
> This is starting to smell like an opportunity to use the gitlink stuff,
> isn't it?
I'd agree that we could have a submodule in /doc/git/html/. This way,
even users of msysGit and GitMe would benefit.
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-29 23:25 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-28 23:07 A tour of git: the basics (and notes on some unfriendly messages) Carl Worth
2007-09-29 0:00 ` Shawn O. Pearce
2007-09-29 0:49 ` Johannes Schindelin
2007-09-29 7:44 ` Steffen Prohaska
2007-09-29 15:06 ` Johannes Schindelin
2007-09-29 16:06 ` Steffen Prohaska
2007-09-29 16:05 ` [PATCH] WinGit: included /bin/start in the installer Steffen Prohaska
2007-09-29 16:05 ` [PATCH] WinGit: include html pages from official git.git's html branch Steffen Prohaska
2007-09-29 20:50 ` Johannes Schindelin
2007-09-29 22:13 ` Junio C Hamano
2007-09-29 23:23 ` Johannes Schindelin [this message]
2007-09-30 8:19 ` Steffen Prohaska
2007-09-29 9:01 ` A tour of git: the basics (and notes on some unfriendly messages) Pierre Habouzit
2007-09-29 10:45 ` [RFC] patch series to sketch a less verbose and frightening output Pierre Habouzit
2007-09-29 10:49 ` Pierre Habouzit
[not found] ` <1191062758-30631-2-git-send-email-madcoder@debian.org>
2007-09-29 14:33 ` [PATCH 1/4] Rework progress module so that it uses less screen lines, with progress bars Nicolas Pitre
2007-09-29 16:07 ` Pierre Habouzit
2007-09-30 12:45 ` A tour of git: the basics (and notes on some unfriendly messages) Wincent Colaiuta
2007-09-30 13:49 ` Pierre Habouzit
2007-09-30 14:31 ` Wincent Colaiuta
2007-09-29 21:48 ` Steffen Prohaska
2007-09-29 22:25 ` Junio C Hamano
2007-09-30 8:15 ` Steffen Prohaska
2007-09-30 10:17 ` Junio C Hamano
2007-09-30 12:44 ` Johannes Schindelin
2007-09-30 13:41 ` Steffen Prohaska
2007-09-29 0:45 ` Junio C Hamano
2007-09-30 3:38 ` Carl Worth
2007-09-30 3:38 ` Carl Worth
2007-09-29 5:32 ` Nguyen Thai Ngoc Duy
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=Pine.LNX.4.64.0709300022080.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=prohaska@zib.de \
/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).