Re: [PATCH v3 00/14] Clean up how fetch_pack() handles the heads list
- From
Junio C Hamano <gitster@pobox.com>
- Date
- Sep 17, 2012, 20:39 UTC
- Message-ID
- <7vr4q0tmd3.fsf@alter.siamese.dyndns.org>
- In-Reply-To
- <50571DC9.2030602@alum.mit.edu>
Michael Haggerty <mhagger@alum.mit.edu> writes:
Show 6 quoted lines
> It is interesting that you consider the sort order of string_list to be > somewhat of an internal implementation detail. I had thought of its > current behavior as being the obvious thing and considered it part of > the API's contract. For example, the current sort order is already > observable via the API through iteration or by calling > print_string_list().
You can prepare an unsorted string list that holds items in the order you desire, and call print_string_list() on it. I do not think we ever promised to keep using the same sort order when you allow the string list to use sorted insertion by calling the "sorted" API functions.