git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: jrnieder@uchicago.edu
Cc: git@vger.kernel.org, Alex Riesen <raa.lkml@gmail.com>,
	Jeff King <peff@peff.net>
Subject: Re: [RFC/PATCH] Documentation: Don't assume git-sh-setup and git-parse-remote are in the PATH
Date: Sun, 29 Jun 2008 12:08:53 -0700	[thread overview]
Message-ID: <7vbq1kawje.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: Pine.GSO.4.62.0806291026310.8371@harper.uchicago.edu

jrnieder@uchicago.edu writes:

> How about this documentation patch? (This time tested! With hg-fast-export
> appropriately modified:
>   $ hg clone http://hg.sharesource.org/asciidoc
>   $ mkdir asciidoc-git && cd asciidoc-git
>   $ git init && hg-fast-export.sh -r /path/to/asciidoc --quiet
>   $ git checkout
>   $ sudo ./install.sh
>   $ cd /path/to/git/Documentation && make git-{sh-setup,parse-remote}.html
> I haven't tried rebuilding manpages, though.)
>
> Junio: I stole the commit message from you. I hope you don't mind.

I don't, but reading the script again, I suspect it is not clear enough
that the user is also responsible for setting up GIT_DIR appropriately
before using it, perhaps by sourcing git-sh-setup.  We probably would want
to add it in a separate patch.

  reply	other threads:[~2008-06-29 19:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-27 20:10 [RFC/PATCH] Documentation: Don't assume git-sh-setup and git-parse-remote are in the PATH Jonathan Nieder
2008-06-28 20:58 ` Alex Riesen
2008-06-28 21:05   ` Junio C Hamano
2008-06-29  5:38     ` Jeff King
2008-06-29 16:10       ` jrnieder
2008-06-29 19:08         ` Junio C Hamano [this message]
2008-06-30  2:39           ` 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=7vbq1kawje.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=jrnieder@uchicago.edu \
    --cc=peff@peff.net \
    --cc=raa.lkml@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).