From: Dirk Behme <dirk.behme@googlemail.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: Git tree updated
Date: Fri, 16 Mar 2007 19:57:14 +0100 [thread overview]
Message-ID: <45FAE88A.1090904@googlemail.com> (raw)
In-Reply-To: <20070301143330.GF26097@atomide.com>
Tony Lindgren wrote:
> Now we have following branches:
>
> linus
> \
> omap-fixes
> \
> omap-upstream
> \
> omap-drivers
> \
> master
>
> The branches have following purpose:
>
> linus Linus' mainline tree
> omap-fixes Queue of omap fixes for -rcN series
Looks like this starts to work:
http://www.ussg.iu.edu/hypermail/linux/kernel/0703.2/0246.html
http://www.uwsg.iu.edu/hypermail/linux/kernel/0703.0/2536.html
-> search for "OMAP"
:)
How do the changes in omap-fixes find their way to Linus?
Does Linus pull directly from omap-fixes? How is this triggered?
Cheers
Dirk
next prev parent reply other threads:[~2007-03-16 18:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-01 14:33 Git tree updated Tony Lindgren
2007-03-16 18:57 ` Dirk Behme [this message]
2007-03-19 12:39 ` tony
-- strict thread matches above, loose matches on Subject: below --
2007-05-08 3:19 Tony Lindgren
2007-05-08 12:05 ` Trilok Soni
2007-05-08 16:26 ` Tony Lindgren
2007-05-08 17:45 ` Woodruff, Richard
2007-05-08 17:51 ` Syed Mohammed, Khasim
2007-05-08 17:58 ` Tony Lindgren
2007-05-08 18:02 ` Syed Mohammed, Khasim
2007-05-08 18:19 ` Tony Lindgren
2007-05-08 18:44 ` Syed Mohammed, Khasim
2007-05-10 15:49 ` Dirk Behme
2007-05-10 16:03 ` Tony Lindgren
2007-07-11 13:04 Tony Lindgren
2007-07-11 16:51 ` Syed Mohammed, Khasim
2007-07-11 23:24 ` Kyungmin Park
[not found] ` <ae36f8040707111843m274eb2fdlc0c38042c6af8daa@mail.gmail.com>
2007-07-12 1:44 ` Luís Vitório Cargnini
2007-07-12 2:03 ` Nishanth Menon
2007-07-12 2:18 ` Luís Vitório Cargnini
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=45FAE88A.1090904@googlemail.com \
--to=dirk.behme@googlemail.com \
--cc=linux-omap-open-source@linux.omap.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox