All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: git@vger.kernel.org
Subject: What's cooking for today
Date: Tue, 08 Apr 2014 14:10:38 -0700	[thread overview]
Message-ID: <xmqqr45734tt.fsf@gitster.dls.corp.google.com> (raw)

As I do not want to send the full "what's cooking" report back to
back, here is just a highlight of updates.

A handful of topics are now in 'master', including:

 - Fix for mis-used "nor", by Justin Lebar.

 - MSVC port fixes, by Marat Radchenko.

 - Portability fixes for gmtime sanity checking, by Peff.

Also a few topics are now in 'next', expected to be kept there for
the rest of this cycle, including:

 - Compute the patch-id in a way that is stable with use of "git
   diff -O<order>", which is unfortunately backward incompatible, by
   Michael S. Tsirkin.

 - Update the internal of "diff-tree" so that it can be used to
   compare N trees (not just 2), and use it to optimize "diff
   -c/--cc", by Kirill Smelkov.

I am also hoping that a few other topics can join 'next' to be
cooked for the rest of this cycle, including:

 - "Ref-transaction" series by Michael.

 - "Interpret-Trailers" series by Christian.

Thanks.

                 reply	other threads:[~2014-04-08 21:10 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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