From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/4] Add ability to auto spawn screen on a controlling terminal
Date: Mon, 24 Sep 2012 15:32:32 +0100 [thread overview]
Message-ID: <1348497152.8662.9.camel@ted> (raw)
In-Reply-To: <1347921831-60604-1-git-send-email-jason.wessel@windriver.com>
On Mon, 2012-09-17 at 17:43 -0500, Jason Wessel wrote:
> This is a series of 4 patches, 2 for bitbake and 2 for oe-core. On
> the bitbake side the idea is to have a new type of event which can
> exec a command or print a log message if there is no controlling
> terminal available.
>
> When a controlling terminal is available the knotty UI can directly
> execute the command on the controlling terminal, instead of printing
> something, which occurs in all the other UI's. What is really nice
> about this is that you don't have to spawn screen in separate
> terminals when you only want to use a single terminal to a build
> server.
Merged to master, thanks.
Richard
prev parent reply other threads:[~2012-09-24 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-17 22:43 [PATCH 0/4] Add ability to auto spawn screen on a controlling terminal Jason Wessel
2012-09-17 22:43 ` [PATCH 1/4] progress.py: Fix traceback when running goggle ui Jason Wessel
2012-09-17 22:43 ` [PATCH 2/4] event.py, knotty.py, ncurses.py, runningbuild.py: Add support for LogExecTTY event Jason Wessel
2012-09-17 22:43 ` [PATCH 3/4] terminal: pass data store all the way through to terminal class Jason Wessel
2012-09-17 22:43 ` [PATCH 4/4] terminal: Send LogExecTTY event to spawn screen Jason Wessel
2012-09-24 14:32 ` Richard Purdie [this message]
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=1348497152.8662.9.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jason.wessel@windriver.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 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.