From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Jonas Fonseca <fonseca@diku.dk>
Cc: Petr Baudis <pasky@ucw.cz>, git@vger.kernel.org
Subject: Re: [PATCH] Cogito documentation updates
Date: 20 Nov 2005 07:37:07 -0800 [thread overview]
Message-ID: <86veyn49gc.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20051120101112.GA2302@diku.dk>
>>>>> "Jonas" == Jonas Fonseca <fonseca@diku.dk> writes:
Jonas> - local cg-fetch now works without the cp option -u
But it still requires cp -d, unless some other patch fixed that recently.
--
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!
next prev parent reply other threads:[~2005-11-20 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-20 10:11 [PATCH] Cogito documentation updates Jonas Fonseca
2005-11-20 15:37 ` Randal L. Schwartz [this message]
2005-11-23 12:16 ` Jonas Fonseca
2005-11-23 14:33 ` Randal L. Schwartz
2005-11-23 14:58 ` Andreas Ericsson
2005-11-23 19:52 ` Junio C Hamano
2005-11-23 17:29 ` Linus Torvalds
2005-11-27 15:28 ` Petr Baudis
2005-11-26 19:12 ` Jonas Fonseca
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=86veyn49gc.fsf@blue.stonehenge.com \
--to=merlyn@stonehenge.com \
--cc=fonseca@diku.dk \
--cc=git@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.
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.