From: Neil Horman <nhorman@tuxdriver.com>
To: Jay Rolette <rolette@infiniteio.com>
Cc: Dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Process question: reviewing older patches
Date: Wed, 28 Jan 2015 16:23:59 -0500 [thread overview]
Message-ID: <20150128212359.GA4801@hmsreliant.think-freely.org> (raw)
In-Reply-To: <CADNuJVr59okZAzBQR4Z7YYaiNcyZOoURA1=VdGg0c1R6tmJEZQ@mail.gmail.com>
On Wed, Jan 28, 2015 at 02:57:58PM -0600, Jay Rolette wrote:
> Thanks Thomas and Neil. Sadly, no joy. While I generally like gmail for my
> mail, there's not a reasonable way to import the mbox file or to control
> the message id.
>
Sure there is, you just need to select an appropriate MUA. You can't use the
web interface for this. Enable imap access to your gmail account, and setup an
MUA like mutt to point to it. Then the mutt client can open the mbox file, or
you can fill out the in-reply-to: header manually.
Neil
next prev parent reply other threads:[~2015-01-28 21:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-28 15:52 Jay Rolette
2015-01-28 16:22 ` Thomas Monjalon
2015-01-28 16:49 ` Neil Horman
2015-01-28 20:57 ` Jay Rolette
2015-01-28 21:23 ` Neil Horman [this message]
2015-01-29 13:38 ` Jay Rolette
2015-01-29 14:14 ` Neil Horman
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=20150128212359.GA4801@hmsreliant.think-freely.org \
--to=nhorman@tuxdriver.com \
--cc=dev@dpdk.org \
--cc=rolette@infiniteio.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).