netdev - Re: [PATCH 00/13] net: dsa: lan9303: unicast offload, fdb,mdb,STP

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 25 Jul 2017 09:34:15 +0200
From:   Egil Hjelmeland <egil.hjelmeland@...itel.com>
To:     Florian Fainelli <f.fainelli@...il.com>, <corbet@....net>,
        <andrew@...n.ch>, <vivien.didelot@...oirfairelinux.com>,
        <davem@...emloft.net>, <kernel@...gutronix.de>,
        <linux-doc@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
        <netdev@...r.kernel.org>
Subject: Re: [PATCH 00/13] net: dsa: lan9303: unicast offload, fdb,mdb,STP

On 24. juli 2017 18:54, Florian Fainelli wrote:
> 
> First thing would be to get your patch submissions square, because the
> patches do not appear to have been sent as a reply to this cover letter,
> and worse yet, they are all appearing with their commit date, which is
> highly confusing since that makes them go back in time for some of them.
> 

Hi all!

I am very sorry for the email-thread mess. Once the emails showed up on 
the spinics mirror I realized I had made a fool of my self. I see now 
that I have to add --thread to "git format-patch", when _not_ using 
"git send-email" as the backend. (I did not get "git send-email" to work
with the company email server.)

I had noted that "git format-patch" preserved commit dates, but I
wrongly thought that was "a feature, not a bug". From now on I will
make sure to "git rebase --ignore-date master".

Egil

DISCLAIMER:
This e-mail may contain confidential and privileged material for the sole use of the intended recipient. Any review, use, distribution or disclosure by others is strictly prohibited. If you are not the intended recipient (or authorized to receive for the recipient), please contact the sender by reply e-mail and delete all copies of this message.