From: Wim Van Sebroeck <wim@iguana.be>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-next@vger.kernel.org,
Linux Watchdog Mailing List <linux-watchdog@vger.kernel.org>,
Linus <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Change of the linux-watchdog-next tree location
Date: Thu, 15 Mar 2012 21:32:36 +0100 [thread overview]
Message-ID: <20120315203004.GA4824@infomag> (raw)
In-Reply-To: <20111025185229.GY11844@infomag.iguana.be>
Hi Stephen,
Could you change the location of the linux-watchdog-next tree to the following tree and branch:
git://www.linux-watchdog.org/linux-watchdog-next.git master
Kind regards,
Wim.
next prev parent reply other threads:[~2012-03-15 20:32 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-13 6:43 currently missing kernel devel trees Stephen Rothwell
2011-10-13 11:26 ` Josh Boyer
2011-10-13 12:36 ` Dave Airlie
2011-10-13 13:33 ` Stephen Rothwell
2011-10-13 13:53 ` Dave Airlie
2011-10-13 13:54 ` Stephen Rothwell
2011-10-13 15:15 ` Bob Copeland
2011-10-13 23:00 ` Stephen Rothwell
2011-10-13 18:35 ` Konrad Rzeszutek Wilk
2011-10-14 0:21 ` Randy Dunlap
2011-10-14 0:33 ` Stephen Rothwell
2011-10-14 1:03 ` Phillip Lougher
2011-10-24 9:20 ` Stephen Rothwell
2011-11-02 17:32 ` Phillip Lougher
2011-11-03 1:18 ` Stephen Rothwell
2011-10-14 3:25 ` Mike Frysinger
2011-10-15 17:57 ` Mike Frysinger
2011-10-24 9:38 ` Stephen Rothwell
2011-10-16 21:11 ` Wim Van Sebroeck
2011-10-24 9:50 ` Stephen Rothwell
2011-10-25 18:52 ` Wim Van Sebroeck
2012-03-15 20:32 ` Wim Van Sebroeck [this message]
2012-03-15 22:06 ` Change of the linux-watchdog-next tree location Stephen Rothwell
2011-10-26 20:45 ` currently missing kernel devel trees David Teigland
2011-10-29 6:50 ` Stephen Rothwell
2011-10-28 2:58 ` Guan Xuetao
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=20120315203004.GA4824@infomag \
--to=wim@iguana.be \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-watchdog@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.org \
/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.