Good point! Doing that now :)
> On Nov 17, 2015, at 9:47 AM, P. Taylor Goetz <[email protected]> wrote:
>
> Cool!
>
> For the purpose of discussion, it might be a good idea to annotate the PDF to
> give each one a number for easier reference. Otherwise we’ll have to
> reference them by description (e.g. “The green one with the ‘m’ inside the
> newt’s tail.” ;) )
>
> -Taylor
>
>
>> On Nov 17, 2015, at 12:32 PM, aditi hilbert <[email protected]> wrote:
>>
>> Thanks, all. I just created MYNEWT-12
>> <https://issues.apache.org/jira/browse/MYNEWT-12>.
>>
>> aditi
>>
>>
>>> On Nov 17, 2015, at 9:21 AM, P. Taylor Goetz <[email protected]> wrote:
>>>
>>> Confirming that no attachments were received on your reply.
>>>
>>> Looks like another route is in order. JIRA attachments might be the easiest
>>> route.
>>>
>>> -Taylor
>>>
>>>> On Nov 17, 2015, at 12:12 PM, Marvin Humphrey <[email protected]>
>>>> wrote:
>>>>
>>>> On Tue, Nov 17, 2015 at 7:32 AM, aditi hilbert <[email protected]> wrote:
>>>>> I did attach the document with 4 drawings of “mynewt” to my mail. I am
>>>>> going
>>>>> to try a second time with the original drawings of 6 “mynewts". Please
>>>>> ignore the first page with drawings of newt on it. The following two pages
>>>>> should show a total of 6 drawings. Hope you can see them this time!
>>>>
>>>> It seems that this emailing list is configured to strip attachments. As
>>>> extra
>>>> confirmation, I've attached the Incubator's egg logo to this email; I
>>>> predict
>>>> you won't see it, though because of gmail's quirky deduping I probably
>>>> will.
>>>>
>>>> The easiest way to share an image is probably to open a MYNEWT Jira issue
>>>> and
>>>> attach it there, or possibly just to commit the files to the site svn repo.
>>>> For text there are lots of other options such as paste.apache.org, Github
>>>> gists or pull requests, and so on, but for images there's not a perfect
>>>> answer
>>>> that I know of. The downside is that we won't be able to view them in our
>>>> browsers without downloading first because of MIME type issues (unless you
>>>> commit to svn and fiddle with the svn properties), but since the target
>>>> audience is developers, it's not unreasonable to ask us to figure things
>>>> out.
>>>>
>>>> Marvin Humphrey
>>>
>>
>