From: William Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] X11R7.5 git branch
Date: Mon, 01 Mar 2010 15:04:57 +0000 [thread overview]
Message-ID: <4B8BD799.3040008@carallon.com> (raw)
In-Reply-To: <4B8AB776.40204@gmail.com>
On 28/02/2010 18:35, Paulius Zaleckas wrote:
> Hi,
>
> As we have discussed earlier I have put all my X11R7.5 work in:
>
> git://gitorious.org/takeme-buildroot/takeme-buildroot.git x11r75
>
> Should I post patch series to the list?
> I am waiting for your comments on my work!
Paulius, have started look at what you have done. Good work,
depressingly similar to all the work I have done, but oh well.
One thing I have noticed is that you have quite a few changes in there
that are not related to x11, any chance of splitting those out as
separate patches as don't want them to complicate review.
Peter - what do you suggest should be the process for getting this in,
most of it looks good but there are a few places where I think things
can be improved. Should Paulius and I try to get a master repository
that we both sign off on?
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
next prev parent reply other threads:[~2010-03-01 15:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-28 18:35 [Buildroot] X11R7.5 git branch Paulius Zaleckas
2010-03-01 15:04 ` William Wagner [this message]
2010-03-01 20:47 ` Paulius Zaleckas
2010-03-02 9:08 ` William Wagner
2010-03-02 9:15 ` Thomas Petazzoni
2010-03-02 12:33 ` Paulius Zaleckas
2010-03-02 8:43 ` Thomas Petazzoni
2010-03-02 9:02 ` William Wagner
2010-03-02 12:31 ` Paulius Zaleckas
2010-03-08 13:30 ` Peter Korsgaard
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=4B8BD799.3040008@carallon.com \
--to=will_wagner@carallon.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 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.