From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: git fetch over ssh trouble
Date: Fri, 26 Jan 2007 09:23:56 -0500 [thread overview]
Message-ID: <20070126142356.GA1947@fieldses.org> (raw)
In-Reply-To: <7vejpi2u91.fsf@assigned-by-dhcp.cox.net>
On Thu, Jan 25, 2007 at 10:10:34PM -0800, Junio C Hamano wrote:
> "J. Bruce Fields" <bfields@fieldses.org> writes:
>
> >> 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.
>
> Saying "let's grab everything" is certainly tempting, but I
> think it is a bit too much.
Yeah.
> How about doing this instead, then?
Works for me, thanks!
bfields@pickle:git$ git fetch linux-nfs
Password:
Nothing specified for fetching with remote.linux-nfs.fetch
Password:
Oh, OK, the password requests are a little excessive. I should go
generate an ssh key.
--b.
prev parent reply other threads:[~2007-01-26 14:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-26 5:08 git fetch over ssh trouble J. Bruce Fields
2007-01-26 5:24 ` Junio C Hamano
2007-01-26 5:34 ` J. Bruce Fields
2007-01-26 6:10 ` Junio C Hamano
2007-01-26 14:23 ` J. Bruce Fields [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=20070126142356.GA1947@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).