From: "Marc-F. Lucca-Daniau" <mfld.fr@gmail.com>
To: Marcin Laszewski <marcin.laszewski@gmail.com>
Cc: ELKS <Linux-8086@Vger.Kernel.Org>, jody Bruchon <jody@jodybruchon.com>
Subject: Re: BusyELKS
Date: Fri, 7 Feb 2020 20:25:27 +0100 [thread overview]
Message-ID: <2ae816d1-92a9-15a5-d954-58dfca495e78@gmail.com> (raw)
In-Reply-To: <CABdhv6LPtqYoj1ix0fhbAchfXfAHd4gsgVM0ieb1xQ8ix=xHiA@mail.gmail.com>
Hello Marcin,
I was speechless when opening your archive... wow, what a contribution !
I opened a PR on Github in order for you to verify that your patches
were correctly applied:
https://github.com/elks-org/elks/pull/310
Thank you !
MFLD
Le 06/02/2020 à 14:16, Marcin Laszewski a écrit :
> Hello Jody & Marc,
>
> I have added some patches to busyelks (int attachement). What do you
> thing about it?
>
> ml.
next parent reply other threads:[~2020-02-07 19:25 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CABdhv6LPtqYoj1ix0fhbAchfXfAHd4gsgVM0ieb1xQ8ix=xHiA@mail.gmail.com>
2020-02-07 19:25 ` Marc-F. Lucca-Daniau [this message]
[not found] ` <CABdhv6KNay6z+MbPRkpwSOmw8Qw9ox_R99ONeHyCfD8VwiO1kw@mail.gmail.com>
2020-02-10 20:14 ` BusyELKS Marc-F. Lucca-Daniau
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=2ae816d1-92a9-15a5-d954-58dfca495e78@gmail.com \
--to=mfld.fr@gmail.com \
--cc=Linux-8086@Vger.Kernel.Org \
--cc=jody@jodybruchon.com \
--cc=marcin.laszewski@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).