From: Ross Burton <ross.burton@intel.com>
To: "Damian, Alexandru" <alexandru.damian@intel.com>
Cc: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 3/3] Initial commit for wayland/weston 1.0.3
Date: Mon, 24 Dec 2012 09:14:14 +0000 [thread overview]
Message-ID: <1CD17EA59464401087B5B319D15D9437@intel.com> (raw)
In-Reply-To: <CAJ2CSBvgHoB-oDR5qu7rsK5erCO+kCf+UEGjwcURnYtm5dWQ0A@mail.gmail.com>
On Monday, 24 December 2012 at 08:00, Damian, Alexandru wrote:
> One should follow the wayland website for HOWTO-s and testing
> instructions.
>
> Opening a terminal emulator and starting "weston" is the easiest way
> to get started, regardless if one is under X or in console.
>
> I don't think the patch comment is the proper place to document this,
> should I add a wiki page ?
Yes, a wiki page with status, known issues, and what's next is a good idea.
Ross
next prev parent reply other threads:[~2012-12-24 9:29 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-20 16:48 [PATCH 0/3] Initial wayland integration Alex DAMIAN
2012-12-20 16:48 ` [PATCH 1/3] Wayland userspace library initial 1.0.3 Alex DAMIAN
2012-12-20 16:48 ` [PATCH 2/3] Initial commit for wayland/weston 1.0.3 Alex DAMIAN
2012-12-20 16:48 ` [PATCH 3/3] Prepare mesa-dri for weston compatibility Alex DAMIAN
2012-12-20 17:17 ` Martin Jansa
2012-12-20 17:20 ` Burton, Ross
2012-12-21 10:10 ` Damian, Alexandru
2012-12-21 10:53 ` Burton, Ross
2012-12-21 11:37 ` [PATCH v2 0/3] Initial wayland integration Alex DAMIAN
2012-12-21 11:38 ` [PATCH 1/3] Wayland userspace library initial 1.0.3 Alex DAMIAN
2012-12-21 11:46 ` Burton, Ross
2012-12-21 11:38 ` [PATCH 2/3] Initial commit for wayland/weston 1.0.3 Alex DAMIAN
2012-12-21 11:49 ` Burton, Ross
2012-12-21 11:38 ` [PATCH 3/3] Prepare mesa-dri for weston compatibility Alex DAMIAN
2012-12-21 11:51 ` Burton, Ross
2012-12-21 11:47 ` [PATCH 0/3] Initial wayland integration Burton, Ross
2012-12-21 12:38 ` Damian, Alexandru
2012-12-21 12:43 ` Burton, Ross
2012-12-21 12:45 ` Damian, Alexandru
2012-12-21 12:51 ` [PATCH v3 " Alex DAMIAN
2012-12-21 12:51 ` [PATCH 1/3] Wayland userspace library initial 1.0.3 Alex DAMIAN
2012-12-21 12:51 ` [PATCH 2/3] Prepare mesa-dri for weston compatibility Alex DAMIAN
2012-12-21 16:49 ` Burton, Ross
2012-12-21 12:51 ` [PATCH 3/3] Initial commit for wayland/weston 1.0.3 Alex DAMIAN
2012-12-21 15:46 ` Burton, Ross
2012-12-24 8:00 ` Damian, Alexandru
2012-12-24 9:14 ` Ross Burton [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-12-24 9:57 [PATCH 1/3] Wayland userspace library initial 1.0.3 Alex DAMIAN
2012-12-24 9:57 ` [PATCH 0/3] Initial wayland integration Alex DAMIAN
2012-12-24 9:57 ` [PATCH 3/3] Initial commit for wayland/weston 1.0.3 Alex DAMIAN
2013-01-04 11:04 ` Burton, Ross
2013-01-04 15:21 ` Burton, Ross
2013-01-04 17:49 ` Saul Wold
2013-01-07 16:06 [PATCH 1/3] Wayland userspace library initial 1.0.3 Alex DAMIAN
2013-01-07 16:06 ` [PATCH v4 0/3] Initial wayland integration Alex DAMIAN
2013-01-07 16:06 ` [PATCH 3/3] Initial commit for wayland/weston 1.0.3 Alex DAMIAN
2013-01-08 9:58 ` Burton, Ross
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=1CD17EA59464401087B5B319D15D9437@intel.com \
--to=ross.burton@intel.com \
--cc=alexandru.damian@intel.com \
--cc=openembedded-core@lists.openembedded.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