From: Felipe Balbi <me@felipebalbi.com>
To: Koen Kooi <koen@dominion.thruhere.net>
Cc: Tony Lindgren <tony@atomide.com>, Anand Gadiyar <gadiyar@ti.com>,
l-o List <linux-omap@vger.kernel.org>
Subject: Re: 2.6.37-omap1 tag?
Date: Wed, 12 Jan 2011 22:05:08 +0200 [thread overview]
Message-ID: <1294862708.1717.2.camel@eowin> (raw)
In-Reply-To: <CA2B2459-D659-4CA9-9D1C-09C65A37DDE6@dominion.thruhere.net>
Hi,
On Wed, 2011-01-12 at 19:03 +0100, Koen Kooi wrote:
> Op 11 jan 2011, om 17:34 heeft Tony Lindgren het volgende geschreven:
>
> > * Anand Gadiyar <gadiyar@ti.com> [110111 03:04]:
> >> Koen Kooi wrote:
> >>> Are there any plans to do a 2.6.37-omap1 tag?
> >>
> >> Given that linux-omap is now closely tracking mainline, is
> >> this still needed?
> >
> > Those tags are no longer needed, the mainline kernel is now the
> > stable kernel and should be used as the base for any distros
> > or products.
>
> It turns out that l-o head (.37-rc8 currently) and Linus' .37differ a lot, so after spending an evening fruitlessly trying to rebase my patches on top of Linus' .37 I decided to go the other way and just do 'git format-patch v2.6.37-rc8..v2.6.37', apply those on top of l-o rc8 and then rebase my patchset on top of that. That was 5 minutes of work.
>
> regards,
>
> Koen--
> To unsubscribe from this list: send the line "unsubscribe linux-omap" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
balbi
next prev parent reply other threads:[~2011-01-12 20:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-11 9:51 2.6.37-omap1 tag? Koen Kooi
2011-01-11 11:05 ` Anand Gadiyar
2011-01-11 16:34 ` Tony Lindgren
2011-01-12 18:03 ` Koen Kooi
2011-01-12 19:04 ` Paul Walmsley
2011-01-12 20:05 ` Felipe Balbi [this message]
2011-01-12 20:06 ` Felipe Balbi
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=1294862708.1717.2.camel@eowin \
--to=me@felipebalbi.com \
--cc=gadiyar@ti.com \
--cc=koen@dominion.thruhere.net \
--cc=linux-omap@vger.kernel.org \
--cc=tony@atomide.com \
/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.