From: Andreas Ericsson <ae@op5.se>
To: Junio C Hamano <junkio@cox.net>
Cc: "Randal L. Schwartz" <merlyn@stonehenge.com>,
git@vger.kernel.org, Nicolas Pitre <nico@cam.org>
Subject: Re: [BUG] OSX ends with "install: git-init.1: No such file or directory"
Date: Thu, 11 Jan 2007 10:57:31 +0100 [thread overview]
Message-ID: <45A60A0B.5000001@op5.se> (raw)
In-Reply-To: <7vmz4q5abe.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> merlyn@stonehenge.com (Randal L. Schwartz) writes:
>
>> If I cd into Documentation, and try to make "git-init.1", I get this:
>>
>> % make git-init.1
>> asciidoc -b docbook -d manpage -f asciidoc.conf git-init.txt
>> xmlto -m callouts.xsl man git-init.xml
>> Note: meta date : No date. Using generated date git-init-db
>> Note: meta source : No productname or alternative git-init-db
>> Note: meta source : No refmiscinfo@class=source git-init-db
>> Note: meta version: No productnumber or alternative git-init-db
>> Note: meta version: No refmiscinfo@class=version git-init-db
>> Warn: meta source : No valid fallback. Leaving empty git-init-db
>> Note: meta manual : No ancestor with title git-init-db
>> Note: meta manual : No refmiscinfo@class=manual git-init-db
>> Warn: meta manual : No valid fallback. Leaving empty git-init-db
>> Note: Writing git-init-db.1
>> rm git-init.xml
>>
>> That's not good. Making git-init-db when it wants git-init.
>
> Not good. I am _very_ tempted to do this.
>
Perhaps, but "git init-db" does a lot more than just initialise the
object database (such as setting default config-variables, installing
template hooks...). "git init" is actually a more sensible name now adays.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2007-01-11 9:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 5:51 [BUG] OSX ends with "install: git-init.1: No such file or directory" Randal L. Schwartz
2007-01-11 6:47 ` Junio C Hamano
2007-01-11 9:57 ` Andreas Ericsson [this message]
2007-01-11 17:28 ` Horst H. von Brand
2007-01-11 23:53 ` Junio C Hamano
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=45A60A0B.5000001@op5.se \
--to=ae@op5.se \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=merlyn@stonehenge.com \
--cc=nico@cam.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.