All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gelonida N <gelonida@gmail.com>
To: git@vger.kernel.org
Subject: Re: How to properly rename a repository with submodules
Date: Sun, 20 May 2012 20:49:13 +0200	[thread overview]
Message-ID: <jpbeb9$cni$1@dough.gmane.org> (raw)
In-Reply-To: <jpbcjj$ho$1@dough.gmane.org>

On 05/20/2012 08:19 PM, Gelonida N wrote:
> Hi,
>
> Today I noticed to my surprise, that a repository with submodules
> contains absolute paths.in the .git file of each sub module.
>
> This is kind of surprising to me and seems to make it absolutely
> impossible to have a non bare git repository on a memory stick.
>
> It also seems to make it impossible to rename a working repository after
> cloning.
>
> So I have three questions.
>
> 1.) Is there any way to force git to use relative path names, such, that
> this issue just disappears.
>
> 2,) Is there any existing script, that allows me to move a git
> repository to another location without breaking it's sub modules.
>
> 3.) Why do these path names have to be absolute? Is this for performance
> reasons? path names relative to the location of the .git file seem to be
> much more flexible / portable.
>

It seems this behaviur is just on one of my 'new' machines which was 
upgraded to
Ubuntu 12.04 (git version 1.7.9.5)


on my old machines I had either really old git versions or the most 
recent ones 1.7.10


I just added ppa:git-core/ppa to the Ubuntu sources and upgraded git to 
1.7.10

Problem solved!! Path names are now relative. So it seems it wasn't only 
me thinking absolute path names are a bad idea :-)

      reply	other threads:[~2012-05-20 18:49 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-20 18:19 How to properly rename a repository with submodules Gelonida N
2012-05-20 18:49 ` Gelonida N [this message]

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='jpbeb9$cni$1@dough.gmane.org' \
    --to=gelonida@gmail.com \
    --cc=git@vger.kernel.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.