git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eric Wong <e@80x24.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "Nicolas Pitre" <nico@cam.org>,
	"Lukas Sandström" <luksan@gmail.com>
Subject: Re: What's cooking in git.git (Aug 2016, #02; Thu, 4)
Date: Thu, 4 Aug 2016 23:34:35 +0000	[thread overview]
Message-ID: <20160804233435.GA31403@dcvr> (raw)
In-Reply-To: <xmqqshukyxqw.fsf@gitster.mtv.corp.google.com>

Junio C Hamano <gitster@pobox.com> wrote:
> [Graduated to "master"]

> * ew/http-walker (2016-07-18) 4 commits
>   (merged to 'next' on 2016-07-18 at a430a97)
>  + list: avoid incompatibility with *BSD sys/queue.h
>   (merged to 'next' on 2016-07-13 at 8585c03)
>  + http-walker: reduce O(n) ops with doubly-linked list

Yay!  This finally introduces the Linux kernel linked list
into git.  I'm not sure if it's worth the effort to introduce
cleanup commits to start using it in places where we already
have doubly-linked list implementations:

(+Cc Nicolas and Lukas)
* sha1_file.c delta_base_cache_lru is open codes this
* builtin/pack-redundant.c could probably be adapted, too
 ... any more?

And there may be other places where we have performance problems
walking singly-linked lists and would be better off on a
doubly-linked one (or even just readability ones).

<snip>

>  cf. <alpine.DEB.2.20.1607061016330.6426@virtualbox>
>  cf. <CACsJy8AiER_=5aJ65r+GPCE_nXbrPTAMKJi=FuJgT8zzV2-NFw@mail.gmail.com>

It might be useful for new-to-mailing-lists folks to note that
these are Message-IDs references which can be looked up at the
following locations:

	mid.mail-archive.com/%s
	marc.info/?i=%s
	public-inbox.org/git/%s/
	mid.gmane.org/%s		# currently down

ref: https://en.wikipedia.org/wiki/Message-ID

  parent reply	other threads:[~2016-08-04 23:36 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-04 22:28 What's cooking in git.git (Aug 2016, #02; Thu, 4) Junio C Hamano
2016-08-04 22:56 ` Mike Hommey
2016-08-04 23:32   ` Junio C Hamano
2016-08-04 23:39     ` Mike Hommey
2016-08-08  6:48     ` Torsten Bögershausen
2016-08-08  6:50       ` Mike Hommey
2016-08-04 23:10 ` Philip Oakley
2016-08-04 23:32   ` Junio C Hamano
2016-08-04 23:34 ` Eric Wong [this message]
2016-08-05  6:25   ` Junio C Hamano
2016-08-05  7:45   ` Jeff King
2016-08-05  8:02     ` Eric Wong
2016-08-05  8:11       ` Jeff King
2016-08-05  8:26         ` Eric Wong
2016-08-05  8:34           ` Jeff King
2016-08-05  9:14             ` Eric Wong
2016-08-07  9:06 ` 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=20160804233435.GA31403@dcvr \
    --to=e@80x24.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=luksan@gmail.com \
    --cc=nico@cam.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).