From: Timur Tabi <timur@freescale.com>
To: Patrik Gornicz <patrik-git@mail.pgornicz.com>
Cc: <git@vger.kernel.org>
Subject: Re: git-fetch does not work from .git subdirectory
Date: Mon, 26 Nov 2012 10:09:18 -0600 [thread overview]
Message-ID: <50B3942E.2020001@freescale.com> (raw)
In-Reply-To: <50AD77F3.3080702@mail.pgornicz.com>
Patrik Gornicz wrote:
> Just a hunch but your remote's location uses a relative path
> '../linux-2.6.git', perhaps git is messing up what the path is relative
> to.
That makes sense. Git is looking at the URL and not realizing that it's
relative to the home directory.
[remote "upstream"]
url = ../linux-2.6.git/
fetch = +refs/heads/*:refs/remotes/upstream/*
> Note sure what the fix will be though as it'll likely break existing
> repositories that use relative paths either way. Can you try an
> absolute path to see if that fixes thing?
If I change that to
[remote "upstream"]
url = /home/b04825/git/linux-2.6.git/
fetch = +refs/heads/*:refs/remotes/upstream/*
then everything works.
IMHO, this is a bug in git.
--
Timur Tabi
Linux kernel developer at Freescale
prev parent reply other threads:[~2012-11-26 16:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-20 22:24 git-fetch does not work from .git subdirectory Timur Tabi
2012-11-22 0:55 ` Patrik Gornicz
2012-11-26 16:09 ` Timur Tabi [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=50B3942E.2020001@freescale.com \
--to=timur@freescale.com \
--cc=git@vger.kernel.org \
--cc=patrik-git@mail.pgornicz.com \
/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).