From: "Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>
To: git@vger.kernel.org
Subject: bug: request-pull broken when remote name contains a slash
Date: Fri, 14 Jan 2011 10:06:45 +0100 [thread overview]
Message-ID: <20110114090645.GA13060@pengutronix.de> (raw)
Hello,
the remotes in my linux repo look as follows:
[remote "ptx/ukl"]
url = git://git.pengutronix.de/git/ukl/linux-2.6.git
push = +refs/heads/*:refs/heads/*
fetch = +refs/heads/*:refs/remotes/ptx/ukl/*
[remote "ptx/otheruser"]
url = git://git.pengutronix.de/git/otheruser/linux-2.6.git
fetch = +refs/heads/*:refs/remotes/ptx/otheruser/*
[remote "ptx/yetanotheruser"]
url = git://git.pengutronix.de/git/yetanotheruser/linux-2.6.git
fetch = +refs/heads/*:refs/remotes/ptx/yetanotheruser/*
unfortunately this makes sending request pulls uncomfortable:
ukl@octopus:~/gsrc/linux-2.6$ git request-pull HEAD^ ptx/ukl
The following changes since commit a08948812b30653eb2c536ae613b635a989feb6f:
Merge branch 'hwmon-for-linus' of git://git.kernel.org/pub/scm/linux/kernel/git/groeck/staging (2011-01-10 08:57:46 -0800)
are available in the git repository at:
ptx/ukl mxs/for-2.6.38
...
The reason for that is in git-parse-remote.sh:get_data_source() which
assumes that a remote with a slash is a filename and so get_remote_url
doesn't use $(git config --get "remote.$1.url") but ptx/ukl directly.
Best regards
Uwe
--
Pengutronix e.K. | Uwe Kleine-König |
Industrial Linux Solutions | http://www.pengutronix.de/ |
next reply other threads:[~2011-01-14 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-14 9:06 Uwe Kleine-König [this message]
2011-01-14 11:36 ` [PATCH] fix git-parse-remote.sh for remotes that contain slashes Stefan Naewe
2011-01-14 19:55 ` Junio C Hamano
2011-02-28 9:36 ` [PATCH] get_remote_url(): use the same data source as ls-remote to get remote urls Uwe Kleine-König
2011-02-28 23:38 ` Junio C Hamano
2011-03-01 8:41 ` Uwe Kleine-König
2011-03-01 9:21 ` [PATCH 1/2] " Uwe Kleine-König
2011-03-01 9:21 ` [PATCH 2/2] git-request-pull: open-code the only invocation of get_remote_url Uwe Kleine-König
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=20110114090645.GA13060@pengutronix.de \
--to=u.kleine-koenig@pengutronix.de \
--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 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).