git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Dec 2013, #05; Thu, 26)
Date: Fri, 27 Dec 2013 14:13:35 -0800	[thread overview]
Message-ID: <7vmwjmj628.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAPig+cQXsdFocFeSR8YKh8crOwBFP0ZK0td2UbP-yypRYJhREQ@mail.gmail.com> (Eric Sunshine's message of "Fri, 27 Dec 2013 16:54:52 -0500")

Eric Sunshine <sunshine@sunshineco.com> writes:

> On Thu, Dec 26, 2013 at 4:08 PM, Junio C Hamano <gitster@pobox.com> 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'.
>>
>> You can find the changes described here in the integration branches
>> of the repositories listed at
>>
>>     http://git-blame.blogspot.com/p/git-public-repositories.html
>>
>> --------------------------------------------------
>> [New Topics]
>
> Would $gmane/239575 [1] be of interest for "New Topics"?
>
> [1]: http://article.gmane.org/gmane.comp.version-control.git/239575/

Actually I was planning to scoop it up directly to master but forgot
to do so.

Running "git diff maint pu -- name-hash.c" shows that we have added
a comment that mentions index_name_exists---that needs to be
adjusted, too, by the way.

  reply	other threads:[~2013-12-27 22:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-26 21:08 What's cooking in git.git (Dec 2013, #05; Thu, 26) Junio C Hamano
2013-12-27 21:54 ` Eric Sunshine
2013-12-27 22:13   ` Junio C Hamano [this message]
2014-01-02 20:47     ` Eric Sunshine
2014-01-02 21:11       ` Junio C Hamano
2014-01-02 21:37         ` Eric Sunshine

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=7vmwjmj628.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=sunshine@sunshineco.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 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).