git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Ericsson <ae@op5.se>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: git@vger.kernel.org
Subject: Re: still unclear on setting up a repository
Date: Sun, 20 Nov 2005 02:07:44 +0100	[thread overview]
Message-ID: <437FCC60.3090100@op5.se> (raw)
In-Reply-To: <86br0g883v.fsf@blue.stonehenge.com>

Randal L. Schwartz wrote:
> And then, another "go-boom" problem:
> 
>     % cg-fetch
>     Hard links don't work - using copy
>     Fetching head...
>     cp: illegal option -- d


I think this was resolved some weeks ago. Perhaps you could try the 
latest cogito from git://git.kernel.org/pub/scm/cogito/cogito.git ?

> 
> Any chance you could make this more POSIX-like?  I know you have a big
> warning in README.osx, but are you *really* needing all those weird
> GNU-isms?  Maybe you could fall back to using rsync to copy exactly
> what you need?
> 

There aren't that many. This particular one was a typo, iirc.

As for rsync; From the output you posted above, you were setting up both 
the repositories on your local machine. Using rsync for those cases 
would be pretty stupid.

On a side-note, could you please turn off your spamvertising auto-reply? 
It sends me some info about your perl-expertise and contact-numbers 
every now and then. It's getting a bit annoying.

-- 
Andreas Ericsson                   andreas.ericsson@op5.se
OP5 AB                             www.op5.se
Tel: +46 8-230225                  Fax: +46 8-230231

  reply	other threads:[~2005-11-20  1:07 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-20  0:40 still unclear on setting up a repository Randal L. Schwartz
2005-11-20  1:07 ` Andreas Ericsson [this message]
2005-11-20  1:14   ` Randal L. Schwartz
2005-11-20  2:10     ` Andreas Ericsson
2005-11-27 14:50     ` Petr Baudis
2005-11-27 23:15 ` Petr Baudis

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=437FCC60.3090100@op5.se \
    --to=ae@op5.se \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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).