From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>,
Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: [PATCH 0/5] More builtin-fetch fixes
Date: Tue, 18 Sep 2007 04:54:44 -0400 [thread overview]
Message-ID: <20070918085444.GN3099@spearce.org> (raw)
Yet another round of builtin-fetch fixes. This series fixes the
latest breakage in `pu` for this topic along with an annoying
warning when using the http transport.
The third patch in the series is a behavior change for git-fetch.
The commit message discusses it in detail. Junio and I kicked this
around on #git earlier this morning.
At this point myself and a few other experienced-with-Git coworkers
are running this builtin-fetch "in production" for all daily tasks.
We don't use *everything* that the tool supports as I did not know
about this breakage in branch.$name.merge until tonight when Junio
mentioned it, but for some of the really common cases we are quite
happy with builtin-fetch. Especially its performance as we're
seeing speedups of 25x or more on Cygwin/Windows.
I still believe there's work yet to be done on this topic as I'm
quite sure the transfer.unpackLimit is not being honored. I meant
to look at that tonight but wound up wasting all night and morning on
the 3rd patch of this series. I will try to work on the unpackLimit
issue Tuesday or Wednesday this week.
--
Shawn.
next reply other threads:[~2007-09-18 8:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-18 8:54 Shawn O. Pearce [this message]
2007-09-18 10:16 ` [PATCH 0/5] More builtin-fetch fixes Andreas Ericsson
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=20070918085444.GN3099@spearce.org \
--to=spearce@spearce.org \
--cc=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.