From: Christopher Li <sparse@chrisli.org>
To: Luc Van Oostenryck <luc.vanoostenryck@gmail.com>
Cc: Linux-Sparse <linux-sparse@vger.kernel.org>
Subject: Re: master merge plans
Date: Tue, 22 Aug 2017 10:47:08 -0400 [thread overview]
Message-ID: <CANeU7QkQR6b936UR3VoYuzLGYdiOcTM=SaWtifsRNeF0rKhP+g@mail.gmail.com> (raw)
In-Reply-To: <CAExDi1QryT9Hc6+yY0_E4Y6opsq3JiYo0KOidSDSj4VGD0J1Nw@mail.gmail.com>
On Tue, Aug 22, 2017 at 9:32 AM, Luc Van Oostenryck
<luc.vanoostenryck@gmail.com> wrote:
>
> Nicolai's constexpr series.
>
Is that constexpr-v4 branch on your git repository you want me to merge?
If you have a newer one, please post the git url.
Chris
next prev parent reply other threads:[~2017-08-22 14:47 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-21 19:39 master merge plans Christopher Li
2017-08-22 13:32 ` Luc Van Oostenryck
2017-08-22 14:47 ` Christopher Li [this message]
2017-08-22 15:51 ` Christopher Li
2017-08-22 20:05 ` Luc Van Oostenryck
2017-08-23 20:50 ` Christopher Li
2017-08-29 11:27 ` Christopher Li
2017-09-03 19:24 ` Luc Van Oostenryck
2017-08-22 14:53 ` Dibyendu Majumdar
2017-08-22 14:59 ` Christopher Li
2017-09-03 20:26 ` Simple SSA status Luc Van Oostenryck
2017-09-04 18:29 ` Christopher Li
2017-09-04 20:07 ` Luc Van Oostenryck
2017-09-04 20:37 ` Dibyendu Majumdar
2017-09-04 20:55 ` Luc Van Oostenryck
2017-09-04 21:24 ` Dibyendu Majumdar
2017-09-04 23:31 ` Christopher Li
2017-09-05 0:55 ` Luc Van Oostenryck
2017-09-05 3:28 ` Christopher Li
2017-09-07 2:03 ` Luc Van Oostenryck
2017-09-07 2:15 ` Linus Torvalds
2017-09-07 2:55 ` Christopher Li
2017-09-07 3:17 ` Luc Van Oostenryck
2017-09-07 4:04 ` Christopher Li
2017-09-07 4:49 ` Luc Van Oostenryck
2017-09-07 6:17 ` Christopher Li
2017-09-07 7:38 ` Luc Van Oostenryck
2017-09-07 3:05 ` Luc Van Oostenryck
2017-09-07 2:20 ` Christopher Li
2017-09-07 3:46 ` Luc Van Oostenryck
2017-09-07 4:02 ` Christopher Li
2017-09-07 4:24 ` Luc Van Oostenryck
2017-09-07 4:33 ` Christopher Li
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='CANeU7QkQR6b936UR3VoYuzLGYdiOcTM=SaWtifsRNeF0rKhP+g@mail.gmail.com' \
--to=sparse@chrisli.org \
--cc=linux-sparse@vger.kernel.org \
--cc=luc.vanoostenryck@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).