From: "Sudarshan S Chawathe" <chaw@eip10.org>
To: Per Bothner <per@bothner.com>
Cc: kawa <kawa@sourceware.org>
Subject: Re: Threads and the getResult method
Date: Sun, 19 Mar 2017 14:25:00 -0000 [thread overview]
Message-ID: <17664.1489933553@vereq.eip10.org> (raw)
In-Reply-To: Your message of "Sat, 18 Mar 2017 23:19:13 -0700." <b3d02d55-c2e7-a3e4-539e-408155448562@bothner.com>
> From: Per Bothner <per@bothner.com>
> Date: Sat, 18 Mar 2017 23:19:13 -0700
> Generally, I'm as comfortable (or more so) with patches, since I'm
> more familiar with that workflow, especially when I'm the one
> submitting changes :-) In this case, since you create a pull request,
> I'm happy to do it that way - though a ChangeLog entry would be
> appreciated.
I just added a ChangeLog entry to the GitLab repo and it seems to have
made its way to the merge request.
I'll send any future (new) modifications as patches as you suggest.
Regards,
-chaw
prev parent reply other threads:[~2017-03-19 14:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-19 0:01 Sudarshan S Chawathe
2017-03-19 6:20 ` Per Bothner
2017-03-19 14:25 ` Sudarshan S Chawathe [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=17664.1489933553@vereq.eip10.org \
--to=chaw@eip10.org \
--cc=kawa@sourceware.org \
--cc=per@bothner.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 read-only IMAP folder(s) and NNTP newsgroup(s).