From: Marcin Juszkiewicz <openembedded@haerwu.biz>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] add paroli autostart
Date: Fri, 20 Feb 2009 10:35:26 +0100 [thread overview]
Message-ID: <200902201035.30522.openembedded@haerwu.biz> (raw)
In-Reply-To: <1235075079.6859.211.camel@alap>
On Thursday 19 of February 2009 21:24:39 Angus Ainslie wrote:
> packages/images/fso-paroli-image.bb | 12 +++++++++---
> 1 files changed, 9 insertions(+), 3 deletions(-)
> -# no extra apps
> -GTK_INSTALL = ""
> +# not many extra apps
> +GTK_INSTALL = " \
> + vala-terminal \
> +"
Was this block planned to be in this commit too? Looks like got
committed by mistake.
> + paroli-autostart \
As this looks like what that commit had to do (at least description says
it).
Regards,
--
JID: hrw@jabber.org
Website: http://marcin.juszkiewicz.com.pl/
LinkedIn: http://www.linkedin.com/in/marcinjuszkiewicz
next prev parent reply other threads:[~2009-02-20 9:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 20:24 [PATCH] add paroli autostart Angus Ainslie
2009-02-20 9:35 ` Marcin Juszkiewicz [this message]
2009-02-20 14:44 ` Angus Ainslie
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=200902201035.30522.openembedded@haerwu.biz \
--to=openembedded@haerwu.biz \
--cc=openembedded-devel@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