From: Jeff Johnston <jjohnstn@redhat.com>
To: Joel Sherrill <joel.sherrill@oarcorp.com>
Cc: "newlib@sourceware.org" <newlib@sourceware.org>
Subject: Re: Time for another snapshot
Date: Fri, 18 Aug 2017 14:20:00 -0000 [thread overview]
Message-ID: <CAOox84spDYtO2bF8CdWxPpviOJBbm+-EJyM-mmR1AnfdbiQAcA@mail.gmail.com> (raw)
In-Reply-To: <CAOox84tKntGtHORVNe-_RA4-bR93h+D=hc=zM27TuAXJ4nv+gQ@mail.gmail.com>
New snapshot is completed.
-- Jeff J.
On Wed, Aug 9, 2017 at 3:41 PM, Jeff Johnston <jjohnstn@redhat.com> wrote:
> On Wed, Aug 9, 2017 at 3:34 PM, Joel Sherrill <joel.sherrill@oarcorp.com> wrote:
>>
>>
>> On 8/9/2017 2:13 PM, Jeff Johnston wrote:
>>>
>>> One is scheduled for the 18th or 21st (usually around the 20th of the
>>> month). Is that too late?
>>
>>
>> I was hoping to baseline new RTEMS toolsets with
>> Aditya's submissions in newlib and do some testing
>> on his inttypes work before the Google Summer of
>> Code evaluations are due. That schedule calls for
>> students to submit final code and mentors to do
>> evaluation Aug 21-29.
>>
>> Based on that, if it is the 18th during US working
>> hours, I can rebaseline next Friday. That should
>> work out.
>>
>> Does that sound OK?
>
> Sounds fine. The 18th it is.
>
>>
>> Thanks.
>>
>> --joel
>>
>>
>>> -- Jeff J.
>>>
>>> On Wed, Aug 9, 2017 at 12:26 PM, Joel Sherrill
>>> <joel.sherrill@oarcorp.com> wrote:
>>>>
>>>> Hi
>>>>
>>>> Just wondering if with the recent addition of inttypes, etc. it would
>>>> be good to have another snapshot.
>>>>
>>>> Thanks.
>>>>
>>>> --joel
prev parent reply other threads:[~2017-08-18 14:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-09 16:26 Joel Sherrill
2017-08-09 19:13 ` Jeff Johnston
2017-08-09 19:34 ` Joel Sherrill
2017-08-09 19:41 ` Jeff Johnston
2017-08-18 14:20 ` Jeff Johnston [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=CAOox84spDYtO2bF8CdWxPpviOJBbm+-EJyM-mmR1AnfdbiQAcA@mail.gmail.com \
--to=jjohnstn@redhat.com \
--cc=joel.sherrill@oarcorp.com \
--cc=newlib@sourceware.org \
/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).