From: Dominik Brodowski <linux@dominikbrodowski.net>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org
Subject: re-adding pcmcia and cpupowerutils trees
Date: Sat, 3 Mar 2012 14:54:58 +0100 [thread overview]
Message-ID: <20120303135457.GA6669@comet.dominikbrodowski.net> (raw)
In-Reply-To: <20120120114016.995d4f1af74eee173bef79d9@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 350 bytes --]
Hey Stephen,
as my kernel.org account has just been re-activated, it would be great if
you could re-activate the following trees in your list of trees to fetch for
linux-next:
git://git.kernel.org/pub/scm/linux/kernel/git/brodo/pcmcia.git master
git://git.kernel.org/pub/scm/linux/kernel/git/brodo/cpupowerutils.git master
Many thanks,
Dominik
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2012-03-03 14:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-20 0:40 linux-next: dropping trees Stephen Rothwell
2012-03-03 13:54 ` Dominik Brodowski [this message]
2012-03-04 23:18 ` re-adding pcmcia and cpupowerutils trees Stephen Rothwell
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=20120303135457.GA6669@comet.dominikbrodowski.net \
--to=linux@dominikbrodowski.net \
--cc=linux-next@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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