From: Pavel Roskin <proski@gnu.org>
To: git@vger.kernel.org
Cc: Geoff Russell <geoffrey.russell@gmail.com>
Subject: Re: Problem upgrading to 1.4.0
Date: Mon, 12 Jun 2006 22:33:02 -0400 [thread overview]
Message-ID: <1150165982.4297.88.camel@dv> (raw)
In-Reply-To: <7v1wtwh246.fsf@assigned-by-dhcp.cox.net>
On Sat, 2006-06-10 at 19:12 -0700, Junio C Hamano wrote:
> This is the second time this same gotcha caused trouble here. I
> agree it would be sensible to make git-fetch (which is called by
> git-pull) to detect stale entries in the remotes/origin file and
> remote.origin.fetch configuration items.
And while at that, it would be great to download and keep the list of
the remote branches, perhaps when requested with a special switch. It
doesn't mean that all of the branches should be fetched, but it would be
nice to have a list of the available remove branches somewhere.
As it stands now, this functionality is implemented in git-clone, which
it probably not the best place. Users should not be forced to clone the
directory again to find out which branches are available.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2006-06-13 2:33 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-11 0:07 Problem upgrading to 1.4.0 Geoff Russell
2006-06-11 2:12 ` Junio C Hamano
2006-06-13 2:33 ` Pavel Roskin [this message]
2006-06-13 2:48 ` Sean
2006-06-13 2:48 ` Sean
2006-06-13 3:02 ` Pavel Roskin
2006-06-13 3:28 ` Linus Torvalds
2006-06-13 3:56 ` Pavel Roskin
2006-06-13 7:10 ` Geoff Russell
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=1150165982.4297.88.camel@dv \
--to=proski@gnu.org \
--cc=geoffrey.russell@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.