git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: David Turner <dturner@twopensource.com>
To: git mailing list <git@vger.kernel.org>
Cc: Keith McGuigan <kamggg@gmail.com>
Subject: Signing off, for now
Date: Tue, 24 May 2016 15:22:30 -0400	[thread overview]
Message-ID: <1464117750.24478.104.camel@twopensource.com> (raw)

June 3rd will be my last day at Twitter.  I hope that my new job
(starting in July after a month of vacation) will give me time to work
on Git, but I don't know exactly what parts I'll be working on, or on
what schedule.

As a result, some of my patchsets may get significantly less of my
attention.  Also, my twopensource.com email address will (probably) be
going away.  You can reach me on my personal email address at 
novalis@novalis.org.  

Keith McGuigan <kamggg@gmail.com> will be taking over Git work at
Twitter.  You may remember Keith from his diagnosis of the user-after
free which we fixed in "name-hash: don't reuse cache_entry in
dir_entry".  Some of you also met him at Git Merge.

Here is the status on the pending patchsets that I've worked on:

- index-helper/watchman is in pu.  Keith will be interested in
iterating on this series if necessary.

- alternate refs backends: Michael Haggerty is working on a new version
of this.  I don't know if Keith will have time to jump in on this.
Depending on the exact timing of Michael's work, I might have a chance
to do another round on this.

- Protocol v2: I would like to get a new draft of Stefan's series out
before I leave, but no promises.  It's turned out to be a bit more
complicated than I expected to support HTTP.  At worst, I'll toss my
WIP on github and send a link to the list.  

As you may have heard at Git Merge 2015, Twitter uses a journal-based
replication scheme.  We would like to switch to vanilla fetch but are
concerned about performance in the presence of many refs.  Protocol v2
could help with this.  We haven't sent the journal code to the list
because its handling of refs is suboptimal.  A LMDB refs backend would
make that much simpler.  I think I've sent a github link to the list in
the past for that code.

Keith might or might not do some work on protocol v2, depending on his
time and on how Twitter decides to handle fetching.

I've really enjoyed working on Git, and I hope I get the chance to do
more in the future.  Thanks to everyone for wonderful code reviews and
a pleasant environment.  It's been great.

             reply	other threads:[~2016-05-24 19:22 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-24 19:22 David Turner [this message]
2016-05-24 19:42 ` Signing off, for now Junio C Hamano
2016-06-03 18:11 ` David Turner

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1464117750.24478.104.camel@twopensource.com \
    --to=dturner@twopensource.com \
    --cc=git@vger.kernel.org \
    --cc=kamggg@gmail.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).