From: Dushara Jayasinghe <nidujay@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] Add package Prosody
Date: Wed, 6 Sep 2017 23:02:04 +1000 [thread overview]
Message-ID: <20170906130204.GA31626@debian> (raw)
In-Reply-To: <20170906125410.ebi4ip7phfjramhu@sapphire.tkos.co.il>
> Not needed. Your first attempt was seen on the list.
Ok sorry about the noise
> Please send patches inline, not as attachments. Using 'git send-email' for
> that should make it easier for you.
>
Ok. I'll look it up. Thanks
Dushara
next prev parent reply other threads:[~2017-09-06 13:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-06 12:47 [Buildroot] Add package Prosody Dushara Jayasinghe
2017-09-06 12:54 ` Baruch Siach
2017-09-06 13:02 ` Dushara Jayasinghe [this message]
2017-09-06 19:57 ` Thomas Petazzoni
-- strict thread matches above, loose matches on Subject: below --
2017-09-06 12:36 nidujay
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=20170906130204.GA31626@debian \
--to=nidujay@gmail.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.