From: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>
To: Brian Magnuson <bdmagnuson@gmail.com>
Cc: Jan Kratochvil <honza@jikos.cz>, linux-input@atrey.karlin.mff.cuni.cz
Subject: Re: [PATCH] new driver for wireless xbox receiver for review
Date: Wed, 30 May 2007 11:02:10 -0400 [thread overview]
Message-ID: <d120d5000705300802v49ef7d29ydbd3e39d99aad214@mail.gmail.com> (raw)
In-Reply-To: <bafd4ab0705300751q67eb54efi1a46779576e0d202@mail.gmail.com>
On 5/30/07, Brian Magnuson <bdmagnuson@gmail.com> wrote:
> On 5/30/07, Jan Kratochvil <honza@jikos.cz> wrote:
> >
> > It is not yet in Linus' tree, but it definitely is in Dmitry input tree.
> >
> http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=commit;h=bad058541d848500b5f2cc049c1082d0b2935b7d
>
> Indeed it is. I think this is just some basic git ignorance on my part. I
> clearly see it in
> the link you provided but if I descend from the tree link starting from top
> commit at
> http://git.kernel.org/?p=linux/kernel/git/dtor/input.git;a=summary
> I get some older
> version of xpad.c. Am I just being dense (likely) or is there something
> wrong?
The topmost commit (time-wise) is on "for-linus" branch of my tree. It
contains bug-fixes and tiny cleanups that I plan to push to Linus
shortly. The main branch is "master" which contains all the stuff that
I want to merge once 2.6.23 opens (that includes xbox, aiptek and
more).
Apparently you are descending into the tree for "for-linus" branch.
--
Dmitry
next prev parent reply other threads:[~2007-05-30 15:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-29 4:39 [PATCH] new driver for wireless xbox receiver for review Brian Magnuson
2007-05-29 15:59 ` Dmitry Torokhov
2007-05-30 0:28 ` Brian Magnuson
2007-05-30 12:40 ` Dmitry Torokhov
2007-05-30 13:47 ` Brian Magnuson
2007-05-30 14:24 ` Jan Kratochvil
2007-05-30 14:51 ` Brian Magnuson
2007-05-30 15:02 ` Dmitry Torokhov [this message]
2007-05-30 15:31 ` Brian Magnuson
2007-05-30 9:51 ` Jiri Kosina
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=d120d5000705300802v49ef7d29ydbd3e39d99aad214@mail.gmail.com \
--to=dmitry.torokhov@gmail.com \
--cc=bdmagnuson@gmail.com \
--cc=honza@jikos.cz \
--cc=linux-input@atrey.karlin.mff.cuni.cz \
/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).