{"thread":{"id":"30569","subject":"How to properly rename a repository with submodules","startedAt":"2012-05-20T18:19:31Z","lastAt":"2012-05-20T18:49:13Z","messageCount":2,"participants":["Gelonida N"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"191768","messageId":"jpbcjj$ho$1@dough.gmane.org","threadId":"30569","inReplyTo":null,"subject":"How to properly rename a repository with submodules","fromName":"Gelonida N","fromEmail":"gelonida@gmail.com","sentAt":"2012-05-20T18:19:31Z","receivedAt":"2012-05-20T18:19:31Z","isPatch":false,"sender":{"key":"gelonida@gmail.com","avatar":null},"body":"Hi,\n\nToday I noticed to my surprise, that a repository with submodules \ncontains absolute paths.in the .git file of each sub module.\n\nThis is kind of surprising to me and seems to make it absolutely \nimpossible to have a non bare git repository on a memory stick.\n\nIt also seems to make it impossible to rename a working repository after \ncloning.\n\nSo I have three questions.\n\n1.) Is there any way to force git to use relative path names, such, that \nthis issue just disappears.\n\n2,) Is there any existing script, that allows me to move a git \nrepository to another location without breaking it's sub modules.\n\n3.) Why do these path names have to be absolute? Is this for performance \nreasons? path names relative to the location of the .git file seem to be \nmuch more flexible / portable.\n\n\nThanks in advance for your answers\n"},{"id":"191769","messageId":"jpbeb9$cni$1@dough.gmane.org","threadId":"30569","inReplyTo":"jpbcjj$ho$1@dough.gmane.org","subject":"Re: How to properly rename a repository with submodules","fromName":"Gelonida N","fromEmail":"gelonida@gmail.com","sentAt":"2012-05-20T18:49:13Z","receivedAt":"2012-05-20T18:49:13Z","isPatch":false,"sender":{"key":"gelonida@gmail.com","avatar":null},"body":"On 05/20/2012 08:19 PM, Gelonida N wrote:\n> Hi,\n>\n> Today I noticed to my surprise, that a repository with submodules\n> contains absolute paths.in the .git file of each sub module.\n>\n> This is kind of surprising to me and seems to make it absolutely\n> impossible to have a non bare git repository on a memory stick.\n>\n> It also seems to make it impossible to rename a working repository after\n> cloning.\n>\n> So I have three questions.\n>\n> 1.) Is there any way to force git to use relative path names, such, that\n> this issue just disappears.\n>\n> 2,) Is there any existing script, that allows me to move a git\n> repository to another location without breaking it's sub modules.\n>\n> 3.) Why do these path names have to be absolute? Is this for performance\n> reasons? path names relative to the location of the .git file seem to be\n> much more flexible / portable.\n>\n\nIt seems this behaviur is just on one of my 'new' machines which was \nupgraded to\nUbuntu 12.04 (git version 1.7.9.5)\n\n\non my old machines I had either really old git versions or the most \nrecent ones 1.7.10\n\n\nI just added ppa:git-core/ppa to the Ubuntu sources and upgraded git to \n1.7.10\n\nProblem solved!! Path names are now relative. So it seems it wasn't only \nme thinking absolute path names are a bad idea :-)\n"}]}