From: Nicolas Pitre <nico@cam.org>
To: Mike Hommey <mh@glandium.org>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>
Subject: Re: [RFC/PATCH] Add a --nosort option to pack-objects
Date: Fri, 07 Dec 2007 16:24:17 -0500 (EST) [thread overview]
Message-ID: <alpine.LFD.0.99999.0712071622150.555@xanadu.home> (raw)
In-Reply-To: <1197061832-8489-1-git-send-email-mh@glandium.org>
On Fri, 7 Dec 2007, Mike Hommey wrote:
> While most of the time the heuristics used by pack-objects to sort the
> given object list are satisfying enough, there are cases where it can be
> useful for the user to sort the list with heuristics that would be better
> suited.
Could you please elaborate on those cases where the current heuristic
would be unsatisfactory?
Nicolas
next prev parent reply other threads:[~2007-12-07 21:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-07 21:10 [RFC/PATCH] Add a --nosort option to pack-objects Mike Hommey
2007-12-07 21:24 ` Nicolas Pitre [this message]
2007-12-07 21:44 ` Mike Hommey
2007-12-07 21:25 ` Junio C Hamano
2007-12-07 21:37 ` Junio C Hamano
2007-12-07 21:46 ` Mike Hommey
2007-12-07 22:20 ` Nicolas Pitre
2007-12-08 8:54 ` Mike Hommey
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=alpine.LFD.0.99999.0712071622150.555@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mh@glandium.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 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).