From: Andy Whitcroft <apw@shadowen.org>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: git fetch -- double fetch
Date: Sun, 7 Oct 2007 22:44:33 +0100 [thread overview]
Message-ID: <20071007214433.GA30833@shadowen.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710071728570.4174@racer.site>
On Sun, Oct 07, 2007 at 05:29:38PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Sat, 6 Oct 2007, Andy Whitcroft wrote:
>
> > I have recently been seeing repeated fetching of some branches. I feel
> > this has happened in at least three of my repos on three distinct
> > projects:
> >
> > apw@pinky$ git fetch origin
> > remote: Generating pack...
> > remote: Done counting 5 objects.
> > remote: Deltifying 5 objects...
> > remote: 100% (5/5) done
> > Unpacking 5 objects...
> > remote: Total 5 (delta 0), reused 0 (delta 0)
> > 100% (5/5) done
> > * refs/remotes/origin/master: fast forward to branch 'master' of ssh://git@abat-dev/var/www/git/abat
> > old..new: ce046f0..41c9dde
> > * refs/remotes/origin/master: fast forward to branch 'master' of ssh://git@abat-dev/var/www/git/abat
> > old..new: ce046f0..41c9dde
>
> What does "git config --get-all remote.origin.fetch" say?
apw@pinky$ git config --get-all remote.origin.fetch
+refs/heads/master:refs/remotes/origin/master
+refs/heads/*:refs/remotes/origin/*
apw@pinky$
I don't think that I did anything to this config, I think that is what
the clone setup for me.
-apw
next prev parent reply other threads:[~2007-10-07 21:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-06 18:57 git fetch -- double fetch Andy Whitcroft
2007-10-07 16:29 ` Johannes Schindelin
2007-10-07 21:44 ` Andy Whitcroft [this message]
2007-10-07 23:14 ` Daniel Barkalow
2007-10-07 23:25 ` Johannes Schindelin
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=20071007214433.GA30833@shadowen.org \
--to=apw@shadowen.org \
--cc=Johannes.Schindelin@gmx.de \
--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.