From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Petr Baudis <pasky@suse.cz>
Cc: git@vger.kernel.org
Subject: Re: proper way to make cg-fetch work from originally git-clone'd tree
Date: 10 Nov 2005 16:13:43 -0800 [thread overview]
Message-ID: <867jbgujm0.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20051111001148.GG30496@pasky.or.cz>
>>>>> "Petr" == Petr Baudis <pasky@suse.cz> writes:
>> cg-merge 2>&1 | grep -v 'already fully merged' && make prefix=/opt/git all install && (cd Documentation && make prefix=/opt/git all install)
Petr> Any reason why you were unable to tell the main make 'doc install-doc'?
Because I didn't see it? :-)
--
Randal L. Schwartz - Stonehenge Consulting Services, Inc. - +1 503 777 0095
<merlyn@stonehenge.com> <URL:http://www.stonehenge.com/merlyn/>
Perl/Unix/security consulting, Technical writing, Comedy, etc. etc.
See PerlTraining.Stonehenge.com for onsite and open-enrollment Perl training!
prev parent reply other threads:[~2005-11-11 0:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-10 13:51 proper way to make cg-fetch work from originally git-clone'd tree Randal L. Schwartz
2005-11-11 0:11 ` Petr Baudis
2005-11-11 0:13 ` Randal L. Schwartz [this message]
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=867jbgujm0.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=git@vger.kernel.org \
--cc=pasky@suse.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.
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).