From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Linux Input <linux-input@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Stephen Rothwell <sfr@canb.auug.org.au>
Subject: Input tree moved back to kernel.org
Date: Mon, 10 Oct 2011 18:12:24 -0700 [thread overview]
Message-ID: <20111011011224.GA11832@core.coreip.homeip.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 497 bytes --]
All,
I have moved input tree back to its original place on kernel.org:
git://git.kernel.org/pub/scm/linux/kernel/git/dtor/input.git
The structure is still the same: 'for-linus' branch for current work and
'next' (same as master) branch for the next merge window. I will try
keeping version on github up to date as well.
Stephen, could you please update linux-next once more?
BTW, does anyone know how one can update project description with
gitolite?
Thanks!
--
Dmitry
[-- Attachment #2: Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2011-10-11 1:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 1:12 Dmitry Torokhov [this message]
2011-10-11 6:40 ` Input tree moved back to kernel.org Stephen Rothwell
2011-10-11 15:54 ` Dmitry Torokhov
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=20111011011224.GA11832@core.coreip.homeip.net \
--to=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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;
as well as URLs for NNTP newsgroup(s).