git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Petr Baudis <pasky@suse.cz>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: cg-admin-setuprepo fails to make a cg-clone'able repo
Date: Fri, 11 Nov 2005 01:13:33 +0100	[thread overview]
Message-ID: <20051111001333.GH30496@pasky.or.cz> (raw)
In-Reply-To: <86wtjg31lo.fsf@blue.stonehenge.com>

Dear diary, on Thu, Nov 10, 2005 at 05:32:35PM CET, I got a letter
where "Randal L. Schwartz" <merlyn@stonehenge.com> said that...
> Repeat by:
> 
>         cg-admin-setuprepo repo
>         cg-clone $(PWD)/repo myview

You should cg-init locally, then cg-admin-setuprepo the public one and
push to it. I updated cg-admin-setuprepo's description wrt. that now.

> Results:
> 
>     defaulting to local storage area
>     Hard links don't work - using copy
>     cp: illegal option -- b
>     usage: cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src target
>            cp [-R [-H | -L | -P]] [-f | -i | -n] [-pv] src1 ... srcN directory
>     cg-fetch: unable to get the HEAD branch
>     cg-clone: fetch failed

But this is actually an entirely unrelated bug, it seems - pretty
strange.  I revived another few months old thread because of this, since
it seems the 'b' was actually a typo and we don't want to pass 'cp' this
argument at all, but something different. Does cloning locally otherwise
work?

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
VI has two modes: the one in which it beeps and the one in which
it doesn't.

  reply	other threads:[~2005-11-11  0:13 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-10 16:32 cg-admin-setuprepo fails to make a cg-clone'able repo Randal L. Schwartz
2005-11-11  0:13 ` Petr Baudis [this message]
2005-11-12 16:51   ` Randal L. Schwartz
2005-11-13  0:29     ` 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=20051111001333.GH30496@pasky.or.cz \
    --to=pasky@suse.cz \
    --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).