All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Duy Nguyen <pclouds@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Mar 2014, #03; Fri, 14)
Date: Mon, 17 Mar 2014 11:05:12 -0700	[thread overview]
Message-ID: <xmqqzjkoem5j.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <CACsJy8B3OPe1B4J8-4v_Oq0ZJpWfms8SmrrbfvYHzJ3WpE8P6w@mail.gmail.com> (Duy Nguyen's message of "Sat, 15 Mar 2014 19:34:18 +0700")

Duy Nguyen <pclouds@gmail.com> writes:

> There are two minor fixes [1] [2] on top of v5, but I'm not going to
> send v6 again unless I see more substantial changes. Just give me a
> signal or something before you merge to next so I have a chance to fix
> them if v6 never comes.
>
> [1] http://article.gmane.org/gmane.comp.version-control.git/243693
> [2] http://article.gmane.org/gmane.comp.version-control.git/243692

Thanks. I'd first need to give you a signal when I replace what was
queued with v5, as I have been way behind on this topic and another
large one from Michael, partly due to the "micro" storm for the past
few weeks.

  reply	other threads:[~2014-03-17 18:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-14 22:09 What's cooking in git.git (Mar 2014, #03; Fri, 14) Junio C Hamano
2014-03-15  8:15 ` Torsten Bögershausen
2014-03-17 17:01   ` Junio C Hamano
2014-03-19 10:53     ` Max Horn
2014-03-19 12:32       ` Max Horn
2014-03-19 17:04       ` Junio C Hamano
2014-03-19 17:21         ` Max Horn
2014-03-19 18:53           ` Junio C Hamano
2014-03-15 12:34 ` Duy Nguyen
2014-03-17 18:05   ` Junio C Hamano [this message]
2014-03-16 18:30 ` Philip Oakley
2014-03-16 23:15   ` Ramkumar Ramachandra
2014-03-17 18:01     ` Junio C Hamano
2014-03-17 22:41     ` Philip Oakley
2014-03-17 17:21   ` Junio C Hamano
2014-03-18  0:16     ` Philip Oakley
2014-03-18  4:40   ` Jeff King

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=xmqqzjkoem5j.fsf@gitster.dls.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=pclouds@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.
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.