From: Rantanplan <rantanplanlechien@free.fr>
To: Jiri Kosina <jkosina@suse.cz>
Cc: Benjamin Tissoires <tissoire@tls.cena.fr>,
Michael Poole <mdpoole@troilus.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
linux-input@vger.kernel.org, Stephane Chatty <chatty@enac.fr>
Subject: Re: [PATCH 3/3] HID: deletion of unused code in hid-magicmouse.
Date: Tue, 09 Mar 2010 13:00:41 +0100 [thread overview]
Message-ID: <4B963869.2010801@free.fr> (raw)
In-Reply-To: <alpine.LNX.2.00.1003090056020.17799@pobox.suse.cz>
My apologies for the inconvenience. After some thought I finally
realized that the smtp server at work did not send any of the mail to
the people outside its domain, i.e. everybody except me...
Michael already reviewed the patch (I send them to the mailing list only
in order not to spam your inboxes, mistake number 2) and send his
comments, so I will resend the patch after including his notes. However,
as Michael said, the patches are a little bit heavy faced to the problem
tackled.
That's why I will answer to its mail instead of creating two threads.
Cheers,
Benjamin
Le 09/03/2010 00:56, Jiri Kosina a écrit :
> On Mon, 8 Mar 2010, Benjamin Tissoires wrote:
>
>> Sorry about that, I'm beginning in sending patch for the kernel. I tried to
>> use the git send-email command, but I saw after that the command just send
>> email to the people I added, but not the mailing list. To be sure to (re)send
>> the last patch, I attached it to be sure to send it "correctly", but not
>> according to the recommended practice.
>>
>> I will resend the whole patch list to the mailing list.
>>
>> The patch you told was not intended to be self-consistant but a final cleanup
>> after the two patches I tried to send before. I splitted them like that in
>> order to keep them human readable as git tried to intrelace the additions and
>> removals, even if they were not related together.
>
> Hi Benjamin,
>
> well, I don't have the 1/3 and 2/3 patches anywhere in my mailboxes
> either ... so please resend those as well.
>
> Thanks,
>
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-03-09 12:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1268065277-30129-1-git-send-email-tissoire@cena.fr>
[not found] ` <1268065277-30129-2-git-send-email-tissoire@cena.fr>
[not found] ` <1268065277-30129-3-git-send-email-tissoire@cena.fr>
[not found] ` <1268065277-30129-4-git-send-email-tissoire@cena.fr>
[not found] ` <1268065277-30129-5-git-send-email-tissoire@cena.fr>
2010-03-08 16:27 ` [PATCH 3/3] HID: deletion of unused code in hid-magicmouse Benjamin Tissoires
2010-03-08 16:30 ` Jiri Kosina
2010-03-08 16:57 ` Benjamin Tissoires
2010-03-08 20:27 ` Michael Poole
2010-03-08 20:51 ` Benjamin Tissoires
2010-03-08 23:56 ` Jiri Kosina
2010-03-09 12:00 ` Rantanplan [this message]
2010-03-10 15:09 ` Jiri Kosina
2010-03-10 15:39 ` Benjamin Tissoires
2010-03-08 21:29 Benjamin Tissoires
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=4B963869.2010801@free.fr \
--to=rantanplanlechien@free.fr \
--cc=chatty@enac.fr \
--cc=dmitry.torokhov@gmail.com \
--cc=jkosina@suse.cz \
--cc=linux-input@vger.kernel.org \
--cc=mdpoole@troilus.org \
--cc=tissoire@tls.cena.fr \
/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).