netdev - Re: [for-next V2 00/17][PULL request] Mellanox mlx5 core driver updates 2016-08-20

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] [day] [month] [year] [list]

Date:   Mon, 22 Aug 2016 11:49:01 -0700 (PDT)
From:   David Miller <davem@...emloft.net>
To:     saeedm@....mellanox.co.il
Cc:     saeedm@...lanox.com, dledford@...hat.com, netdev@...r.kernel.org,
        linux-rdma@...r.kernel.org, leonro@...lanox.com,
        talal@...lanox.com, matanb@...lanox.com
Subject: Re: [for-next V2 00/17][PULL request] Mellanox mlx5 core driver
 updates 2016-08-20

From: Saeed Mahameed <saeedm@....mellanox.co.il>
Date: Mon, 22 Aug 2016 20:56:43 +0300

> Technical question though. Do i need to create a new tag for the new
> pull request? I mean, should the tag always point to the "up to" patch
> in the pull request? or can I just use the same tag for the new pull
> request with different "up to" commit ?

Since you're obviously not going to be asking me to pull the same
set of changes, the tag by definition will have to be different.