All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Brad King <brad.king@kitware.com>
Subject: Re: What's cooking in git.git (Mar 2014, #07; Fri, 28)
Date: Sat, 29 Mar 2014 00:23:03 +0100	[thread overview]
Message-ID: <53360457.1060008@alum.mit.edu> (raw)
In-Reply-To: <xmqqtxai7ym6.fsf@gitster.dls.corp.google.com>

On 03/28/2014 11:21 PM, Junio C Hamano wrote:
> Here are the topics that have been cooking.  Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'.

Junio,

Have you overlooked my ref-transactions series [1], or just not gotten
to it yet?

If you would like a version of the series that already addresses Brad
King's comments, you can get it from my GitHub fork [2], the
"ref-transactions" branch.  I'd be happy to post a v3 to the list if you
prefer, but the only changes since v2 were to a commit message and a
comment so it seems like overkill.

Michael

[1] http://thread.gmane.org/gmane.comp.version-control.git/244857
[2] https://github.com/mhagger/git

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  reply	other threads:[~2014-03-28 23:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-28 22:21 What's cooking in git.git (Mar 2014, #07; Fri, 28) Junio C Hamano
2014-03-28 23:23 ` Michael Haggerty [this message]
2014-03-30  7:51   ` Junio C Hamano
2014-03-31 17:56   ` Ronnie Sahlberg
2014-03-31 20:22     ` Michael Haggerty
2014-03-29 15:44 ` Max Horn
2014-03-30  2:01 ` Duy Nguyen
2014-03-31 22:04   ` Junio C Hamano

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=53360457.1060008@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=brad.king@kitware.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.