From: Ben Peart <peartben@gmail.com>
To: Stefan Beller <sbeller@google.com>, Ben Peart <Ben.Peart@microsoft.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>,
"pclouds@gmail.com" <pclouds@gmail.com>,
"johannes.schindelin@gmx.de" <johannes.schindelin@gmx.de>
Subject: Re: [PATCH v1] test-drop-caches: simplify delay loading of NtSetSystemInformation
Date: Mon, 30 Apr 2018 14:43:31 -0400 [thread overview]
Message-ID: <92ff364a-b46c-2274-a3fd-0b68eaa4159e@gmail.com> (raw)
In-Reply-To: <CAGZ79kZvyFTKadjY11Xu+KcV9OUe-4hbjgPzBDcD52X2nZKCzg@mail.gmail.com>
On 4/30/2018 2:12 PM, Stefan Beller wrote:
> On Mon, Apr 30, 2018 at 7:26 AM, Ben Peart <Ben.Peart@microsoft.com> wrote:
>> Take advantage of the recent addition of support for lazy loading functions
>
> Care to specify "recent additions"? Are these in Git code or somewhere else?
>
> I find this alias handy, as then I can describe commits
> in commit messages via "git gcs <commitish>
>
> alias.gcs=show --date=short -s --pretty='format:%h (%s, %ad)'
>
> Thanks,
> Stefan
>
I guess "recent" is relative. :)
db2f7c48cb (Win32: simplify loading of DLL functions, 2017-09-25)
next prev parent reply other threads:[~2018-04-30 18:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-30 14:26 [PATCH v1] test-drop-caches: simplify delay loading of NtSetSystemInformation Ben Peart
2018-04-30 14:57 ` Duy Nguyen
2018-04-30 15:17 ` Ben Peart
2018-04-30 17:05 ` Eric Sunshine
2018-04-30 18:12 ` Stefan Beller
2018-04-30 18:43 ` Ben Peart [this message]
2018-04-30 19:21 ` Johannes Sixt
2018-05-01 12:46 ` [PATCH v2] " Ben Peart
2018-05-02 6:55 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=92ff364a-b46c-2274-a3fd-0b68eaa4159e@gmail.com \
--to=peartben@gmail.com \
--cc=Ben.Peart@microsoft.com \
--cc=git@vger.kernel.org \
--cc=johannes.schindelin@gmx.de \
--cc=pclouds@gmail.com \
--cc=sbeller@google.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).