git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Lars Schneider <larsxschneider@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Aug 2017, #05; Tue, 22)
Date: Thu, 24 Aug 2017 12:33:58 -0700	[thread overview]
Message-ID: <xmqq1so0wyjd.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <7D99B245-4D22-4C9C-9C43-C8B8656F8E6D@gmail.com> (Lars Schneider's message of "Wed, 23 Aug 2017 23:38:06 +0200")

Lars Schneider <larsxschneider@gmail.com> writes:

> On 22 Aug 2017, at 21:56, 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'.  The ones marked with '.' do not appear in any of
>> the integration branches, but I am still holding onto them.
>> 
>> The second batch of topics are in.  This cycle is going a bit slower
>> than the previous one (as of mid-week #3 of this cycle, we have
>> about 200 patches on 'master' since v2.14, compared to about 300
>> patches in the cycle towards v2.14 at a similar point in the cycle),
>> but hopefully we can catch up eventually.  
>> 
>> I am planning to be offline most of the next week, by the way.
>> 
>> 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
>> 
>> --------------------------------------------------
>> [Graduated to "master"]
>> 
>
> Hi Junio,
>
> just in case this got lost: I posted a patch with an improvement to 
> 2841e8f ("convert: add "status=delayed" to filter process protocol", 
> 2017-06-30) which was merged to master in the beginning of 2.15.
>
> https://public-inbox.org/git/20170820154720.32259-1-larsxschneider@gmail.com/

Thanks for pinging, but next time ping the thread itself if it is
about something that is not in What's cooking report you are
responding to.


  reply	other threads:[~2017-08-24 19:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-22 19:56 What's cooking in git.git (Aug 2017, #05; Tue, 22) Junio C Hamano
2017-08-23  1:00 ` Brandon Williams
2017-08-23 21:38 ` Lars Schneider
2017-08-24 19:33   ` Junio C Hamano [this message]
2017-09-15 16:18     ` Johannes Schindelin
2017-09-15 18:33       ` Junio C Hamano
2017-09-15 20:15         ` Johannes Schindelin
2017-09-15 21:22           ` Junio C Hamano
2017-09-18 14:41             ` Johannes Schindelin
2017-09-19  2:32               ` Junio C Hamano
2017-09-19 15:43                 ` Johannes Schindelin
2017-09-19 16:07                   ` Jonathan Nieder
2017-09-29 11:55                     ` Johannes Schindelin
2017-09-19 16:20                   ` Jonathan Nieder
2017-09-19 17:08                   ` Nicolas Morey-Chaisemartin
2017-09-29 12:15                     ` Johannes Schindelin

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=xmqq1so0wyjd.fsf@gitster.mtv.corp.google.com \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=larsxschneider@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).