From: Pratyush Yadav <p.yadav@ti.com>
To: Elijah Newren <newren@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2020, #03; Wed, 12)
Date: Mon, 17 Feb 2020 13:08:31 +0530 [thread overview]
Message-ID: <20200217073829.m3njrrczdbaosynx@ti.com> (raw)
In-Reply-To: <CABPp-BEdrFnSqPnK6FsRqpyP7qZALg_K8JDkdqxnhwkD4yFdzA@mail.gmail.com>
On 15/02/20 08:42PM, Elijah Newren wrote:
> On Wed, Feb 12, 2020 at 2:02 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'. The ones marked with '.' do not appear in any of
> > the integration branches, but I am still holding onto them.
> >
> > The fourth batch of topics are now in 'master'.
>
> Somewhat of a tangent, but is there any plan to update tinyurl.com/gitCal?
Heh, so I'm not the only person who noticed ;-)
--
Regards,
Pratyush Yadav
prev parent reply other threads:[~2020-02-17 7:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-12 21:58 What's cooking in git.git (Feb 2020, #03; Wed, 12) Junio C Hamano
2020-02-13 12:26 ` bw/remote-rename-update-config, was " Johannes Schindelin
2020-02-13 13:02 ` yz/p4-py3, " Johannes Schindelin
2020-02-13 16:06 ` Junio C Hamano
2020-02-13 21:18 ` Junio C Hamano
2020-02-14 4:17 ` Junio C Hamano
2020-02-14 5:15 ` Denton Liu
2020-02-14 14:39 ` Ben Keene
2020-02-14 16:18 ` Junio C Hamano
2020-02-14 17:01 ` Junio C Hamano
2020-02-14 17:05 ` Ben Keene
2020-02-14 18:10 ` Junio C Hamano
2020-03-10 17:38 ` SZEDER Gábor
2020-03-10 18:29 ` Junio C Hamano
2020-02-16 4:42 ` Elijah Newren
2020-02-17 7:38 ` Pratyush Yadav [this message]
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=20200217073829.m3njrrczdbaosynx@ti.com \
--to=p.yadav@ti.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@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.
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).