git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
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:57:27 -0800	[thread overview]
Message-ID: <87vek62n1k.wl%cworth@cworth.org> (raw)
In-Reply-To: <7vmz5i6vqb.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 1229 bytes --]

On Wed, 20 Dec 2006 14:36:12 -0800, Junio C Hamano wrote:
> Carl Worth <cworth@cworth.org> writes:
>
> > 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 ?
>
> Could you check "log master..next" and see if you like what has
> been cooking, please?

Oh, yes, there it is. (I had skimmed the log for master..next but had
missed it---I guess that I also searched for "glob" instead of
"wildcard" didn't help).

Anyway, yes, the description of the new stuff there looks very
interesting, and I'll maybe I'll start running from next a bit to see
how this stuff all works.

I guess the big reason I wrote was that I was surprised to see your
reply instructing Sean on how to update the config file without also
saying something like, "by the way, this need to update the config
file like this will be going away with new work on git-clone that is
being done now and is expected to be in the upcoming git 1.5".

I thought that was the case, but didn't want to say it without
confirming it first. Thanks for confirming it for me.

-Carl

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-12-20 22:58 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
2006-12-20 22:36     ` Junio C Hamano
2006-12-20 22:57       ` Carl Worth [this message]
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=87vek62n1k.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).