From: Paul-Sebastian Ungureanu <ungureanupaulsebastian@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Sep 2018, #04; Thu, 20)
Date: Mon, 24 Sep 2018 00:39:16 +0300 [thread overview]
Message-ID: <38cb30cd-603d-540b-075c-c6378fe13a84@gmail.com> (raw)
In-Reply-To: <xmqqin2zxw55.fsf@gitster-ct.c.googlers.com>
Hello,
On 21.09.2018 08:22, Junio C Hamano wrote:
> The tip of 'next' hasn't been rewound yet. The three GSoC "rewrite
> in C" topics are still unclassified in this "What's cooking" report,
> but I am hoping that we can have them in 'next' sooner rather than
> later. I got an impression that Dscho wanted a chance for the final
> clean-up on some of them, so I am not doing anything hasty yet at
> this moment, though.
Sorry for this late response. I was unexpectedly busy for this period of
time. I will send a new iteration of `stash` tomorrow or Tuesday at the
latest.
Best regards,
Paul
next prev parent reply other threads:[~2018-09-23 21:39 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-21 5:22 What's cooking in git.git (Sep 2018, #04; Thu, 20) Junio C Hamano
2018-09-21 14:30 ` Segfault in master due to 4fbcca4eff Ævar Arnfjörð Bjarmason
2018-09-21 14:34 ` Derrick Stolee
2018-09-21 14:40 ` Ævar Arnfjörð Bjarmason
2018-09-21 14:53 ` Derrick Stolee
2018-09-21 15:55 ` Junio C Hamano
2018-09-21 23:37 ` Ævar Arnfjörð Bjarmason
2018-09-21 23:45 ` Jeff King
2018-09-21 23:49 ` Ævar Arnfjörð Bjarmason
2018-09-21 17:05 ` What's cooking in git.git (Sep 2018, #04; Thu, 20) Johannes Sixt
2018-09-21 17:17 ` Junio C Hamano
2018-09-23 21:39 ` Paul-Sebastian Ungureanu [this message]
2018-10-01 19:16 ` René Scharfe
2018-10-01 20:12 ` Jeff King
2018-10-01 21:37 ` René Scharfe
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=38cb30cd-603d-540b-075c-c6378fe13a84@gmail.com \
--to=ungureanupaulsebastian@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).