From: "Frank Ch. Eigler" <fche@elastic.org>
To: Reinoud Koornstra <reinoudkoornstra@gmail.com>
Cc: overseers@sourceware.org
Subject: Re: account locked
Date: Tue, 05 Nov 2019 20:57:00 -0000 [thread overview]
Message-ID: <20191105205721.GB67437@elastic.org> (raw)
In-Reply-To: <CAAA5faFrJkDY-=xfQbCcL4om_8wdpNKM1fyQZo5D6dTP6tnHaw@mail.gmail.com>
Hi -
> I would like to upload gdb output to a bug filed which I couldn't do,
> because I was blocked. It's contains weird characters as I had to enable
> remote debug. I can't upload it, how can I add it to this case? Thanks,
Try uploading it as a .tar or .zip octet-stream binary?
- FChE
next prev parent reply other threads:[~2019-11-05 20:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-05 18:53 Reinoud Koornstra
2019-11-05 18:59 ` Frank Ch. Eigler
2019-11-05 20:56 ` Reinoud Koornstra
2019-11-05 20:57 ` Frank Ch. Eigler [this message]
2020-06-07 21:10 Sunil Pandey
2020-06-07 21:32 ` Mark Wielaard
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=20191105205721.GB67437@elastic.org \
--to=fche@elastic.org \
--cc=overseers@sourceware.org \
--cc=reinoudkoornstra@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 read-only IMAP folder(s) and NNTP newsgroup(s).