From: Carl Worth <cworth@cworth.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: GIT - error: no such remote ref refs/heads/TestBranch
Date: Wed, 20 Dec 2006 14:31:14 -0800 [thread overview]
Message-ID: <87wt4m2o99.wl%cworth@cworth.org> (raw)
In-Reply-To: <7v64c7pmlw.fsf@assigned-by-dhcp.cox.net>
[-- Attachment #1: Type: text/plain, Size: 965 bytes --]
On Tue, 19 Dec 2006 14:06:03 -0800, Junio C Hamano wrote:
> "Sean Kelley" <sean.v.kelley@gmail.com> writes:
> > error: no such remote ref refs/heads/TestBranch
> > Fetch failure: git+ssh://git.example.com/data/git/proj/kernel/mh.git
> > kelleys@oifig:~/Work/kernel$
> >
> > Any ideas how to correct this?
>
> If you know remote does not have it, then probably not fetching
> from it would be a good idea.
I think a common case is just wanting to track the upstream contents,
whether branches appear or disappear, and being able to do that
without manually maintaining a local configuration file listing the
current remote branches.
Presumably the recently added globbing support would provide that
ability, correct?
Is there any plan to make git-clone take advantage of this capability
so that one can track an upstream that has branches that get
added/remove without having to learn how to manually maintain the
current list of branches in .git/config ?
-Carl
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-12-20 22:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-19 20:33 GIT - error: no such remote ref refs/heads/TestBranch Sean Kelley
2006-12-19 22:06 ` Junio C Hamano
2006-12-20 22:31 ` Carl Worth [this message]
2006-12-20 22:36 ` Junio C Hamano
2006-12-20 22:57 ` Carl Worth
2006-12-20 23:36 ` Junio C Hamano
2006-12-21 6:55 ` Carl Worth
2006-12-21 10:49 ` Peter Baumann
2006-12-22 0:52 ` Junio C Hamano
2006-12-22 2:32 ` Separating "add path to index" from "update content in index" Carl Worth
2006-12-22 3:06 ` Sean
2006-12-22 5:06 ` Nicolas Pitre
2006-12-22 21:57 ` Carl Worth
2006-12-23 5:27 ` Nicolas Pitre
2006-12-24 21:38 ` Daniel Barkalow
2006-12-22 5:10 ` Junio C Hamano
2006-12-22 5:21 ` Shawn Pearce
2006-12-22 8:24 ` Jakub Narebski
2006-12-22 16:18 ` Carl Worth
2006-12-22 17:28 ` Nicolas Pitre
2006-12-22 16:55 ` Carl Worth
2006-12-23 2:56 ` Daniel Barkalow
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=87wt4m2o99.wl%cworth@cworth.org \
--to=cworth@cworth.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).