From: "Shawn O. Pearce" <spearce@spearce.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: [PATCH 0/5] Return of 'quickfetch' version 3
Date: Sun, 11 Nov 2007 02:29:13 -0500 [thread overview]
Message-ID: <20071111072913.GX14735@spearce.org> (raw)
OK, attempt #3. Much shorter series as I've taken out the (messy)
object memory management change. Its now unrelated to this series
and may return in the near future.
1) Fix memory leak in traverse_commit_list
The memory leak we talked about in traverse_commit_list. Its still
valid for pack-objects but is unnecessary for fetch.
2) git-fetch: Always fetch tags if the object they reference exists
I think I figured out why I said "random behavior" earlier.
Please see the commit message for an updated description.
3) run-command: Support sending stderr to /dev/null
4) rev-list: Introduce --quiet to avoid /dev/null redirects
5) git-fetch: avoid local fetching from alternate (again)
Pretty much the original quickfetch series, but updated with list
comments and moved to builtin-fetch where it works for all types
of transports and not just the native git one.
--
Shawn.
reply other threads:[~2007-11-11 7:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20071111072913.GX14735@spearce.org \
--to=spearce@spearce.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 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).