From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org
Cc: linux1394-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: git tree URL for IEEE 1394 (FireWire) kernel subsystem
Date: Mon, 31 Oct 2011 18:57:01 +0100 [thread overview]
Message-ID: <20111031185701.5c8771c6@stein> (raw)
In-Reply-To: <20110918215144.f33db78e54224626c6ee408e@canb.auug.org.au>
[-- Attachment #1: Type: text/plain, Size: 384 bytes --]
Stephen,
please switch the ieee1394/for-next URL once more, now to
git://git.kernel.org/pub/scm/linux/kernel/git/ieee1394/linux1394.git for-next
which is meant to be permanent. (-2.6 suffix of the former name
dropped). Current content is identical with my pull request to
Linus today.
Thanks,
--
Stefan Richter
-=====-==-== =-=- =====
http://arcgraph.de/sr/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-10-31 17:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-17 17:47 git tree URL for IEEE 1394 (FireWire) kernel subsystem Stefan Richter
2011-09-18 11:51 ` Stephen Rothwell
2011-10-31 17:57 ` Stefan Richter [this message]
2011-10-31 23:19 ` 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=20111031185701.5c8771c6@stein \
--to=stefanr@s5r6.in-berlin.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux1394-devel@lists.sourceforge.net \
--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