From: Lars Schneider <larsxschneider@gmail.com>
To: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Apr 2017, #04; Wed, 19)
Date: Thu, 20 Apr 2017 17:32:13 +0200 [thread overview]
Message-ID: <25191991-F4EA-4D91-B291-854F46A34DC2@gmail.com> (raw)
In-Reply-To: <xmqq4lxjabce.fsf@gitster.mtv.corp.google.com>
Sorry for sending this email multiple times. My mobile email client created html... Should be fixed now!
>
> * ls/filter-process-delayed (2017-03-06) 1 commit
> - convert: add "status=delayed" to filter process protocol
>
> What's the status of this one???
> cf. <xmqq60jmnmef.fsf@junio-linux.mtv.corp.google.com>
posted v3 here:
https://public-inbox.org/git/20170409191107.20547-1-larsxschneider@gmail.com/
From my point of view the only open question is if we use an index ("delay-id" favored by Peff) or the path (favored by Taylor) to identify delayed items:
https://public-inbox.org/git/20170227095825.jhdspwy6oa6mvvvm@sigill.intra.peff.net/
https://public-inbox.org/git/20170412173404.GA49694@Ida/#r
I slightly favor the path approach as it simplifies the protocol. But I also trust Peff's opinion.
> * ls/travis-doc-asciidoctor (2017-04-16) 3 commits
> (merged to 'next' on 2017-04-19 at 359c32953b)
> + travis-ci: unset compiler for jobs that do not need one
> + travis-ci: parallelize documentation build
> + travis-ci: build documentation with AsciiDoc and Asciidoctor
>
> Have Travis CI format the documentation with both AsciiDoc and
> AsciiDoctor.
>
> Will merge to 'master'.
Can you hold this until next week?
The I would post a v2 and check asciidoc stderr:
https://public-inbox.org/git/D9F45212-91F7-4BB1-A0EC-74A84DA81860@gmail.com/
I can also post an additional patch if you prefer to merge now.
Thanks, Lars
next prev parent reply other threads:[~2017-04-20 15:32 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 5:37 What's cooking in git.git (Apr 2017, #04; Wed, 19) Junio C Hamano
2017-04-20 9:59 ` Duy Nguyen
2017-04-20 15:35 ` Jeff King
2017-04-20 22:51 ` Junio C Hamano
2017-04-20 22:46 ` Junio C Hamano
2017-04-20 15:32 ` Lars Schneider [this message]
2017-04-20 22:52 ` Junio C Hamano
[not found] ` <D61D47BD-9750-4FB6-892E-013504E03738@gmail.com>
2017-04-20 13:24 ` Johannes Schindelin
2017-04-20 16:56 ` Brandon Williams
2017-04-20 23:18 ` Brandon Williams
2017-04-21 0:56 ` Junio C Hamano
2017-04-20 22:58 ` Junio C Hamano
2017-04-21 9:50 ` Johannes Schindelin
2017-04-21 12:29 ` Christian Couder
2017-04-22 11:48 ` Johannes Schindelin
2017-04-22 17:32 ` Christian Couder
2017-04-24 14:08 ` Johannes Schindelin
2017-04-22 13:37 ` Johannes Sixt
2017-04-24 14:24 ` Johannes Schindelin
2017-04-24 16:34 ` Philip Oakley
2017-04-25 2:17 ` Christian Couder
2017-04-25 2:00 ` Christian Couder
2017-04-25 5:51 ` Johannes Sixt
2017-04-25 6:52 ` Junio C Hamano
2017-04-25 18:26 ` Johannes Sixt
2017-04-24 0:25 ` Junio C Hamano
2017-04-24 14:19 ` Johannes Schindelin
2017-04-24 15:18 ` Ævar Arnfjörð Bjarmason
2017-04-25 0:56 ` 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
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=25191991-F4EA-4D91-B291-854F46A34DC2@gmail.com \
--to=larsxschneider@gmail.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.
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).