From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] Added notes to the mosh package help to clarify run time issues.
Date: Mon, 29 May 2017 22:39:32 +0200 [thread overview]
Message-ID: <20170529223932.2acf7216@free-electrons.com> (raw)
In-Reply-To: <1496082575-24450-1-git-send-email-glbsalazar@gmail.com>
Hello,
On Mon, 29 May 2017 19:29:35 +0100, Gon?alo Salazar wrote:
> Added notes to the mosh package help to clarify some
> issues related with it to ensure mosh will work properly after adding it.
> This includes adding a proper LOCALE on the host and an extra flag when using
> mosh with dropbear.
The commit title should start with the name of the package, i.e:
mosh: add notes to clarify runtime issues
> https://mosh.mit.edu
The notes should go before the upstream URL, and the indentation should
be one tab + two spaces.
> +
> + Mosh requires a host LOCALE matching the client provided LOCALE.
I'm sorry, but I don't understand this sentence.
> + When using mosh with dropbear, a version with the --no-ssh-pty option on
> + the client is required.
And also this one.
So for me, those explanations do not clarify anything :-/
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-05-29 20:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-29 18:29 [Buildroot] [PATCH 1/1] Added notes to the mosh package help to clarify run time issues Gonçalo Salazar
2017-05-29 20:39 ` Thomas Petazzoni [this message]
2017-05-29 21:02 ` Gonçalo Salazar
2017-05-29 21:15 ` Thomas Petazzoni
2017-05-29 21:30 ` Gonçalo Salazar
2017-05-29 21:36 ` Thomas Petazzoni
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=20170529223932.2acf7216@free-electrons.com \
--to=thomas.petazzoni@free-electrons.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox