All of lore.kernel.org
 help / color / mirror / Atom feed
From: Miles Bader <miles.bader@necel.com>
To: git@vger.kernel.org
Subject: git bug? + question
Date: Thu, 02 Nov 2006 14:56:51 +0900	[thread overview]
Message-ID: <buoejsme6ho.fsf@dhapc248.dev.necel.com> (raw)

Hi,

I tried the following sequence of commands to make two clones of a
remote repository, but got an error:

   $ git clone --use-separate-remote ssh://fp.gnu.org/~/git/snogray.git snogray-git
   $ git clone --use-separate-remote --reference snogray-git ssh://fp.gnu.org/~/git/snogray.git imp-sample
   error: refs/reference-tmp/refs/remotes/origin/HEAD points nowhere!

Is this a real error, or bad usage?

Also, a question:  Is there anyway to make git-clone use
--use-separate-remote by default?  I'm trying for a "lots of branches in
a single shared remote repository" style, and use-separate-remote seems
more sane for this usage.

I'm using git version 1.4.3.3.

Thanks,

-Miles

-- 
"I distrust a research person who is always obviously busy on a task."

             reply	other threads:[~2006-11-02  6:01 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-02  5:56 Miles Bader [this message]
2006-11-03  2:40 ` git bug? + question Junio C Hamano
2006-11-03  3:45   ` Sean
2006-11-03  7:48   ` Karl Hasselström
2006-11-03  8:51     ` Junio C Hamano
2006-11-03  9:09       ` Andy Parkins
2006-11-03 19:28         ` Junio C Hamano
2006-11-03  9:46       ` Karl Hasselström
2006-11-03 17:15         ` Josef Weidendorfer
2006-11-03 17:13           ` Jakub Narebski
2006-11-03 19:06             ` Josef Weidendorfer
2006-11-04 12:03           ` Junio C Hamano
2006-11-04 17:50             ` Josef Weidendorfer
2006-11-03  9:59       ` Martin Waitz
2006-11-03 10:27         ` Santi Béjar
2006-11-03 16:10       ` Linus Torvalds
2006-11-03 19:53         ` Junio C Hamano
2006-11-03  8:53     ` Andy Parkins
     [not found]   ` <20061102224549.499610d1.seanlkml@sympatico.ca>
2006-11-03  8:12     ` Karl Hasselström
2006-11-03  9:25       ` Sean
     [not found]       ` <20061103042540.192bbd18.seanlkml@sympatico.ca>
2006-11-03  9:51         ` Karl Hasselström
2006-11-03 20:29         ` Shawn Pearce
2006-11-03 21:27           ` Sean
2006-11-03 23:29           ` Jeff King
2006-11-04  5:10             ` Shawn Pearce
     [not found]           ` <20061103162707.cc8af608.seanlkml@sympatico.ca>
2006-11-04  5:04             ` Shawn Pearce
2006-11-03 20:36     ` Shawn Pearce
2006-11-03 21:24       ` Sean
2006-11-04 12:03         ` Junio C Hamano
2006-11-04 15:33           ` Sean
     [not found]           ` <20061104103325.bfb5e33e.seanlkml@sympatico.ca>
2006-11-04 19:07             ` Shawn Pearce
     [not found]       ` <20061103162422.b0bf105e.seanlkml@sympatico.ca>
2006-11-04  5:03         ` Shawn Pearce
2006-11-04 17:52           ` Josef Weidendorfer
2006-11-04 19:05             ` Shawn Pearce
2006-11-06 11:05               ` Josef Weidendorfer
2006-11-06  9:53             ` Andy Whitcroft
2006-11-06 11:00               ` Josef Weidendorfer
2006-11-06 12:32                 ` Andy Whitcroft

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=buoejsme6ho.fsf@dhapc248.dev.necel.com \
    --to=miles.bader@necel.com \
    --cc=git@vger.kernel.org \
    --cc=miles@gnu.org \
    /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.