From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Steffen Prohaska <prohaska@zib.de>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
Carl Worth <cworth@cworth.org>,
git@vger.kernel.org
Subject: Re: A tour of git: the basics (and notes on some unfriendly messages)
Date: Sat, 29 Sep 2007 16:06:59 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.64.0709291606010.28395@racer.site> (raw)
In-Reply-To: <4D958F04-D531-416A-9FB4-E4119BEC6905@zib.de>
Hi,
On Sat, 29 Sep 2007, Steffen Prohaska wrote:
> On Sep 29, 2007, at 2:49 AM, Johannes Schindelin wrote:
>
> >
> > On Fri, 28 Sep 2007, Shawn O. Pearce wrote:
> >
> > > On Cygwin we have man, so `git help init` (or `git init --help`)
> > > work just fine to display the manual entry. No idea about the MSYS
> > > port.
> >
> > We open the html pages. That is, we don't yet, since we do not
> > generate the html pages just yet; asciidoc is a Python program, and
> > Python is not available as an MSys program as far as I know (and
> > asciidoc insists on finding files in a Unix-like file structure, so we
> > _do_ need an MSys Python).
>
> I propose to clone the html pages from git.git's html branch and include
> them in the installer. I continue to believe that this is the simplest
> and fastest solution for providing html pages.
I'm hesitant... The html branch is synced with the master branch. And we
deviate from the master branch quite a lot ATM.
> I'll provide a patch (hopefully next week).
This will be a good temporary workaround.
Ciao,
Dscho
next prev parent reply other threads:[~2007-09-29 15:08 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 [this message]
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
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.0709291606010.28395@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=cworth@cworth.org \
--cc=git@vger.kernel.org \
--cc=prohaska@zib.de \
--cc=spearce@spearce.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).