Re: git fetch over ssh trouble
- From
- J. Bruce Fields <bfields@fieldses.org>
- Date
- Jan 26, 2007, 05:34 UTC
- Message-ID
- <20070126053400.GB18058@fieldses.org>
- In-Reply-To
- <7vmz462wdh.fsf@assigned-by-dhcp.cox.net>
On Thu, Jan 25, 2007 at 09:24:42PM -0800, Junio C Hamano wrote:
Show 13 quoted lines
> "J. Bruce Fields" <bfields@fieldses.org> writes: > > > Any idea why this is happening?: > > > > bfields@pickle:git$ git fetch linux-nfs > > Password: > > /usr/local/bin/git-parse-remote: line 145: test: !=: unary operator > > expected > > Ouch. > > I wonder what should happen when you do not have anything > defined for "linus-nfs" shorthand.
Oops; I didn't notice that!
> Should it fetch HEAD?
In my case I'd want it to either default to what I actually wanted (+refs/heads/*:refs/remotes/linux-nfs/*), or just fail with something helpful:
"Nothing to fetch"? "No refspec given, and no default fetch configured for linux-nfs"? "What do you want me to fetch?"?
I don't know.
Show 14 quoted lines
>
> diff --git a/git-parse-remote.sh b/git-parse-remote.sh
> index 1122c83..12023d2 100755
> --- a/git-parse-remote.sh
> +++ b/git-parse-remote.sh
> @@ -82,6 +82,7 @@ get_remote_default_refs_for_push () {
> # a merge candidate
> expand_refs_wildcard () {
> first_one=yes
> + test "$#" = 0 && echo empty
> for ref
> do
> lref=${ref#'+'}
> Yep, now it does nothing much more quietly....
--b.