From: Daniel Barkalow <barkalow@iabervon.org>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: pasky@ucw.cz, git@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!)
Date: Tue, 26 Apr 2005 01:18:32 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.21.0504260103050.30848-100000@iabervon.org> (raw)
In-Reply-To: <426DCA75.901@pobox.com>
On Tue, 26 Apr 2005, Jeff Garzik wrote:
> tar xvfj $x
> cd x
> make
> ...
> gcc -g -O2 -Wall '-DSHA1_HEADER=<openssl/sha.h>' -o rpull rpull.c
> libgit.a rsh.c -lz -lssl
> gcc -g -O2 -Wall '-DSHA1_HEADER=<openssl/sha.h>' -o rev-list rev-list.c
> libgit.a -lz -lssl
> gcc -g -O2 -Wall '-DSHA1_HEADER=<openssl/sha.h>' -o git-mktag
> git-mktag.c libgit.a -lz -lssl
> gcc -g -O2 -Wall '-DSHA1_HEADER=<openssl/sha.h>' -o diff-tree-helper
> diff-tree-helper.c libgit.a -lz -lssl
> make: commit-id: Command not found
> Generating cg-version...
>
> So, it still complains about commit-id
In this case, it would complain about .git/HEAD even if it found
commit-id. The right solution is probably to suppress that part if there's
no .git/HEAD.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2005-04-26 5:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 3:24 [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!) Petr Baudis
2005-04-26 3:29 ` Petr Baudis
2005-04-26 4:12 ` Mike Taht
2005-04-26 12:23 ` Petr Baudis
2005-04-26 17:40 ` Paul Jackson
2005-04-26 15:15 ` Martin Atukunda
2005-04-26 4:22 ` Benjamin Herrenschmidt
2005-04-26 4:58 ` Jeff Garzik
2005-04-26 5:18 ` Daniel Barkalow [this message]
2005-04-26 5:40 ` Al Viro
2005-04-26 6:03 ` [PATCH] Don't use commit-id in building Daniel Barkalow
2005-04-26 7:02 ` [ANNOUNCE] Cogito-0.8 (former git-pasky, big changes!) Philip Pokorny
2005-04-26 20:43 ` Petr Baudis
2005-04-26 13:36 ` Morten Welinder
2005-04-26 22:21 ` Pavel Machek
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.21.0504260103050.30848-100000@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pasky@ucw.cz \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).