From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: Andriy Berestovskyy <berestovskyy@gmail.com>
Cc: web@dpdk.org
Subject: Re: [dpdk-web] SSI or similar
Date: Thu, 28 Jan 2016 08:50:23 +0100 [thread overview]
Message-ID: <4049946.aSH1FkcUR2@xps13> (raw)
In-Reply-To: <286A4E7C-7AE8-44BE-81D9-49CBE7843A0A@gmail.com>
2016-01-27 21:50, Andriy Berestovskyy:
> Hi Thomas,
>
> > On 27 Jan 2016, at 15:01, Thomas Monjalon <thomas.monjalon@6wind.com> wrote:
> > Are you volunteer to write such script? Or anyone else?
> > I'd love to have a "make local" command to test website updates.
>
> Sure, no problem. I’ll do this on the weekend.
Great!
Which language would you like to use? (I do not like perl)
next prev parent reply other threads:[~2016-01-28 7:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-14 20:38 Andriy Berestovskyy
2015-12-14 20:53 ` Thomas Monjalon
2015-12-14 21:51 ` Andriy Berestovskyy
2015-12-15 5:43 ` Thomas Monjalon
2015-12-15 22:12 ` Andriy Berestovskyy
2016-01-27 14:01 ` Thomas Monjalon
2016-01-27 20:50 ` Andriy Berestovskyy
2016-01-28 7:50 ` Thomas Monjalon [this message]
2016-01-28 9:48 ` Andriy Berestovskyy
2016-01-28 11:00 ` Thomas Monjalon
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=4049946.aSH1FkcUR2@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=berestovskyy@gmail.com \
--cc=web@dpdk.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 NNTP newsgroup(s).