git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: merlyn@stonehenge.com (Randal L. Schwartz)
To: Petr Baudis <pasky@suse.cz>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: cg-admin-setuprepo fails to make a cg-clone'able repo
Date: 12 Nov 2005 08:51:35 -0800	[thread overview]
Message-ID: <8664qxn71k.fsf@blue.stonehenge.com> (raw)
In-Reply-To: <20051111001333.GH30496@pasky.or.cz>

>>>>> "Petr" == Petr Baudis <pasky@suse.cz> writes:

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

When I tried "local cloning", I first tried to make an empty archive
with cgi-init, but it dumped me into an editor.  I couldn't find a
switch to turn that off.  Perhaps the manpage should say "you'll
be dumped in to an editor", and perhaps provide a way to pass that
message with "-m".

So, on a whim, I realize that it's performing an initial commit, so
I try cg-init -I.  And here's the result:

    localhost:~/Projects/Git % cg-init -I my_master
    defaulting to local storage area
    localhost:~/Projects/Git % cg-clone my_master my_slave
    defaulting to local storage area
    find: /Users/merlyn/Projects/Git/my_master: No such file or directory
    Hard links don't work - using copy
    Fetching head...
    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

So, I guess your answer is no.  What is "-b" for cp.  That's not
on my manpage.

And, after reading the manpage closer, I see my first "my_master"
was created wrong.  But no error message. :(  So, repeating this
using a subdirectory...

    localhost:~/Projects/Git % rm -rf .git 
    localhost:~/Projects/Git % mkdir my_master
    localhost:~/Projects/Git % cd my_master
    localhost:..ects/Git/my_master % cg-init -I
    defaulting to local storage area
    localhost:..ects/Git/my_master % cd ..
    localhost:~/Projects/Git % cg-clone my_master my_slave
    defaulting to local storage area
    Hard links don't work - using copy
    Fetching head...
    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

Again, lots of "no" answers there.

-- 
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!

  reply	other threads:[~2005-11-12 16:52 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
2005-11-12 16:51   ` Randal L. Schwartz [this message]
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=8664qxn71k.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).