From: Felipe Balbi <me@felipebalbi.com>
To: Tony Lindgren <tony@atomide.com>
Cc: twebb <taliaferro62@gmail.com>,
"linux-omap@vger.kernel.org Mailing List"
<linux-omap@vger.kernel.org>
Subject: Re: suggestions for latest code that offers best support of OMAP35x EVM
Date: Thu, 30 Oct 2008 20:12:36 +0200 [thread overview]
Message-ID: <20081030181235.GI32518@frodo> (raw)
In-Reply-To: <20081030174114.GW13227@atomide.com>
On Thu, Oct 30, 2008 at 10:41:15AM -0700, Tony Lindgren wrote:
> * twebb <taliaferro62@gmail.com> [081030 09:22]:
> > Not being very familiar with the kernel development process and git,
> > I'm hoping someone can suggest which code from the l-o git offers the
> > best support of the OMAP35x EVM. I'm guessing it would be the code
> > tagged "v2.6.27-omap1" but I'm not sure. What's the general
> > difference between tags "v2.6.27" and "v2.6.27-omap1"?
>
> The difference is v2.6.27 is a tag by Linus, v2.6.27-omap1 is the
> first patchset of omap patches on top of Linus' v2.6.27.
>
> If we need to add more omap specific fixes on top of that, we'll
> tag v2.6.27-omap2 and so on.
>
> > On a more general note, is there documentation somewhere that
> > describes the kernel development process, and how tags are used (or
> > not) to identify particular stability points in the development
> > lifecycle of a particular tree (like linux-omap)?
>
> There are various git howto sites, also read Documentation/Submit*.
>
> I'm not aware of any docs that would describe the -rc tags and merge
> windows, but I'm sure something like that exists somewhere :)
>
> Anybody got a link?
Documentation/development-process/*
--
balbi
prev parent reply other threads:[~2008-10-30 18:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 16:17 suggestions for latest code that offers best support of OMAP35x EVM twebb
2008-10-30 17:41 ` Tony Lindgren
2008-10-30 18:12 ` Felipe Balbi [this message]
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=20081030181235.GI32518@frodo \
--to=me@felipebalbi.com \
--cc=linux-omap@vger.kernel.org \
--cc=taliaferro62@gmail.com \
--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.