All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boaz Harrosh <bharrosh@panasas.com>
To: Bryan Smith <bryansmi@umich.edu>, open-osd <osd-dev@open-osd.org>,
	Git Mailing List <git@vger.kernel.org>
Subject: Re: tgt submodule?
Date: Sun, 12 Sep 2010 13:39:05 +0200	[thread overview]
Message-ID: <4C8CBBD9.3090409@panasas.com> (raw)
In-Reply-To: <98e3b9f65ffe7883ced7474859b147f4@umich.edu>

On 09/09/2010 10:11 PM, Bryan Smith wrote:
> 
> Sorry for being out of touch for so long, things have been hectic. I've
> been trying to get a final testing solution of VMs set up, and now all of a
> sudden the tgt submodule seems to be inaccessible. When I clone the osc-osd
> source, I receive the following:
> 
> remote: Counting objects: 6559, done.
> remote: Compressing objects: 100% (2445/2445), done.
> remote: Total 6559 (delta 4250), reused 6244 (delta 4024)
> Receiving objects: 100% (6559/6559), 1.33 MiB | 258 KiB/s, done.
> Resolving deltas: 100% (4250/4250), done.
> Submodule 'tgt' (git://git.open-osd.org/tgt/.git) registered for path 'tgt'
> Initialized empty Git repository in
> /home/branches/mikesucks/osc-osd/tgt/.git/
> fatal: The remote end hung up unexpectedly
> Clone of 'git://git.open-osd.org/tgt/.git' into submodule path 'tgt' failed
> 
> Trying to receive the submodule through git from within yields the same
> problem:
> 
> $ sudo git submodule update
> Initialized empty Git repository in
> /home/branches/mikesucks/osc-osd/tgt/.git/
> fatal: The remote end hung up unexpectedly
> Clone of 'git://git.open-osd.org/tgt/.git' into submodule path 'tgt' failed
> 
> From what I've researched on the internet, it seems to me that the source
> itself is having the problem. Do you have any further knowledge of this
> problem? Thanks in advance,
> 
> Bryan Smith
> CITI

Ha, that problem. Rrrr sorry about that. I'm in a catch 22 here, since
I enabled support for http:// cloning the git:// people with old trees and
old instructions have problems.

Here is what to do:
- For new trees do
[]$ git clone --recursive git://git.open-osd.org/osc-osd/.git

  Note the "/.git" at the end. If not supplied then the base tree will
  clone but the tgt submodule will fail. This is because for (dumb) http:
  clones you must supply the "/.git" at the end for it to be found and
  then a "./tgt" submodule path will fail. So I had to do a "../tgt" as
  path for submodule. When you clone as above all is fine but if you clone
  with out the "/.git" the server will be smart enough to find your tree
  by automatically appending the "/.git" directory. But the submodule
  command is no as smart and fails to try the silently added "/.git" directory

If you already cloned or you have an old tree. You can manually edit the
osc-osd/.git/config file to:
diff -Nurp .git/config.old .git/config
--- .git/config.old	2010-09-12 13:24:59.218017002 +0200
+++ .git/config	2010-09-12 13:24:44.283784834 +0200
@@ -5,9 +5,9 @@
 	logallrefupdates = true
 [remote "origin"]
 	fetch = +refs/heads/*:refs/remotes/origin/*
-	url = git://git.open-osd.org/osc-osd
+	url = git://git.open-osd.org/osc-osd/.git
 [branch "master"]
 	remote = origin
 	merge = refs/heads/master
 [submodule "tgt"]
-	url = git://git.open-osd.org/tgt/.git
+	url = git://git.open-osd.org/osc-osd/tgt/.git

[If you have an old tree the [submodule "tgt"] url
 will be OK but the [remote "origin"] url should be fixed
]

At the end you will need to do:
[]$ git remote update
[]$ git submodule update

Again Sorry for your trouble. But if I revert to the old way
then http:// access will not work at all. This way, I sacrifice git://
guys a bit but they still have a way to manage. (One solution
I did not try is having bare trees at server but that will change
every one's config files as well)

Boaz

           reply	other threads:[~2010-09-12 11:39 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <98e3b9f65ffe7883ced7474859b147f4@umich.edu>]

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=4C8CBBD9.3090409@panasas.com \
    --to=bharrosh@panasas.com \
    --cc=bryansmi@umich.edu \
    --cc=git@vger.kernel.org \
    --cc=osd-dev@open-osd.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.