From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] PXA: Drop CERF250 board
Date: Mon, 28 Nov 2011 20:05:47 +0100 [thread overview]
Message-ID: <201111282005.47819.marek.vasut@gmail.com> (raw)
In-Reply-To: <CAPnjgZ0A3j5CZ_4-5uS7k4hwWw_SRmoetP62Ofg9wkCt+TQm3w@mail.gmail.com>
> Hi Marek,
>
> On Mon, Nov 28, 2011 at 9:21 AM, Marek Vasut <marek.vasut@gmail.com> wrote:
> >> Hi Marek,
> >>
> >> On Fri, Nov 25, 2011 at 10:53 AM, Marek Vasut <marek.vasut@gmail.com>
wrote:
> >> > The board is unmaintained and maintainer doesn't respond.
> >>
> >> Should this and the other patches be version 2, or perhaps 3?
> >
> > Probably.
> >
> >> Also I like Mike's suggested phrasing (something like "The board
> >> doesn't build and maintainer doesn't respond") since if it built OK we
> >> would presumably just leave it.
> >
> > I think they don't build, at least that's how it was when I recently
> > tried. And since I don't see any opposing force, let's drop them.
>
> OK, so does that mean you will change the commit message along these
> lines and issue a new version?
>
Wasn't this already pulled in tho?
M
next prev parent reply other threads:[~2011-11-28 19:05 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 18:53 [U-Boot] [PATCH 1/4] PXA: Drop CERF250 board Marek Vasut
2011-11-25 18:53 ` [U-Boot] [PATCH 2/4] PXA: Drop CRADLE board Marek Vasut
2011-11-25 18:53 ` [U-Boot] [PATCH 3/4] PXA: Drop PLEB2 board Marek Vasut
2011-11-25 18:53 ` [U-Boot] [PATCH 4/4] PXA: Drop XM250 board Marek Vasut
2011-11-28 17:12 ` [U-Boot] [PATCH 1/4] PXA: Drop CERF250 board Simon Glass
2011-11-28 17:21 ` Marek Vasut
2011-11-28 17:23 ` Simon Glass
2011-11-28 19:05 ` Marek Vasut [this message]
2011-11-28 19:22 ` Simon Glass
2011-11-28 19:33 ` Marek Vasut
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=201111282005.47819.marek.vasut@gmail.com \
--to=marek.vasut@gmail.com \
--cc=u-boot@lists.denx.de \
/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.