All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tim Gardner <tim.gardner@canonical.com>
To: Tony Lindgren <tony@atomide.com>
Cc: linux-omap@vger.kernel.org
Subject: Re: Important changes, please read
Date: Wed, 14 Jan 2009 09:42:08 -0700	[thread overview]
Message-ID: <496E15E0.70705@canonical.com> (raw)
In-Reply-To: <20090114150502.GN29324@atomide.com>

Tony Lindgren wrote:
>>> - We stop using source.mvista.com git tree, and only use the
>>>  kernel.org git tree. There's no need for having two master trees,
>>>  and kernel.org is the standard way to go. Big thanks to
>>>  Monta Vista for hosting us for many years.

The git path at http://vger.kernel.org/vger-lists.html#linux-omap needs
to be changed.

rtg
-- 
Tim Gardner tim.gardner@canonical.com

  reply	other threads:[~2009-01-14 16:42 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 13:41 Important changes, please read Tony Lindgren
2009-01-14 14:00 ` Koen Kooi
2009-01-14 14:09   ` Tony Lindgren
2009-01-14 14:11     ` Tony Lindgren
2009-01-14 14:15 ` Mika Laitio
2009-01-14 14:28   ` Tony Lindgren
2009-01-14 14:34 ` Felipe Contreras
2009-01-14 15:05   ` Tony Lindgren
2009-01-14 16:42     ` Tim Gardner [this message]
2009-01-15  7:26       ` Tony Lindgren
2009-01-15  9:13         ` Please update linux-omap git link at vger (Re: Important changes, please read) Tony Lindgren
2009-01-15 16:04           ` Please update linux-omap git link at vger David Miller
2009-01-15 16:05             ` Tony Lindgren
2009-01-15 18:41           ` Please update linux-omap git link at vger (Re: Important changes, please read) Matti Aarnio
2009-01-16  7:23             ` Tony Lindgren
2009-01-20 10:26 ` Important changes, please read David Brownell
2009-01-23  1:46   ` Tony Lindgren

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=496E15E0.70705@canonical.com \
    --to=tim.gardner@canonical.com \
    --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.