From: Peter Korsgaard <peter.korsgaard@barco.com>
To: buildroot@busybox.net
Subject: [Buildroot] Matchbox Support
Date: Tue, 15 May 2007 12:55:12 +0200 [thread overview]
Message-ID: <87y7jqwe3z.fsf@sleipner.barco.com> (raw)
In-Reply-To: <005301c796cd$98e56120$6614a8c0@lap> (Assen Stoyanov's message of "Tue, 15 May 2007 11:46:57 +0300")
>>>>> "AS" == Assen Stoyanov <softa@ttechgroup.com> writes:
Hi,
AS> Hello All, I am 99% ready with the port of matchbox
AS> project. Incl.: - Matchbox Window Manager - Matchbox Startup
AS> Notification - Matchbox Desktop - Matchbox Virtual Keyboard
AS> Also other thinks that are 100% done are:
Cool!
AS> My question is - what is the best way to submit all these changes
AS> to the buildroot repository?
Send patches to the bug tracker or this ml.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2007-05-15 10:55 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-10 14:21 [Buildroot] kernel patch not applied David Claffey
2007-05-10 15:34 ` David Claffey
2007-05-11 14:31 ` Hans-Christian Egtvedt
2007-05-11 15:40 ` Bernhard Fischer
2007-05-11 16:29 ` David Claffey
2007-05-12 10:31 ` Bernhard Fischer
2007-05-29 20:52 ` David Claffey
2007-05-14 5:21 ` Hans-Christian Egtvedt
2007-05-14 7:11 ` Bernhard Fischer
2007-05-14 12:41 ` [Buildroot] Matchbox Support Christopher Reder
2007-05-15 8:46 ` Assen Stoyanov
2007-05-15 10:55 ` Peter Korsgaard [this message]
2007-05-14 15:25 ` [Buildroot] kernel patch not applied Hans-Christian Egtvedt
2007-05-14 15:34 ` Bernhard Fischer
2007-05-15 7:47 ` Hans-Christian Egtvedt
2007-05-15 8:53 ` Bernhard Fischer
2007-05-15 10:35 ` [Buildroot] Whats happened to Eric? Ulf Samuelsson
2007-05-15 19:04 ` Erik Andersen
2008-11-04 18:19 ` [Buildroot] kernel patch not applied Julien Boibessot
2008-11-04 19:54 ` Bernhard Reutner-Fischer
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=87y7jqwe3z.fsf@sleipner.barco.com \
--to=peter.korsgaard@barco.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