26/10/2018 02:48, Honnappa Nagarahalli: > > > > 24/10/2018 03:32, Honnappa Nagarahalli: > > > Dharmik Thakkar (1): > > > test/hash: read-write lock-free concurrency test > > > > > > Honnappa Nagarahalli (4): > > > hash: separate multi-writer from rw-concurrency > > > hash: support do not free on delete > > > hash: fix key store element alignment > > > hash: add lock-free read-write concurrency > > > > Please add Cc: sta...@dpdk.org below Fixes: line when the fix must be > > backported. > > > > The script check-git-log.sh will help in this task. > I did not run this script, will run from next time. > > I am confused about when to add 'sta...@dpdk.org'. > https://doc.dpdk.org/guides-18.08/contributing/patches.html section 5.7 says > that while fixing a 'regression' (any issue due to a previous code change), > we should add 'aut...@example.com'. > Then section 5.7.2 says that 'all fix patches to the master that are > candidates for backporting should have 'Cc:sta...@dpdk.org' and should be > CCed to sta...@dpdk.org mailing list. > Last time I CCed a patch to sta...@dpdk.org, I was told not to do it, > 'Cc:sta...@dpdk.org' in the commit message is enough. > > Any clarification would help.
If you add Cc: sta...@dpdk.org in the commit, git-send-email will automatically Cc the email. So the email will be sent to dev and stable at the same time. It's what should happen :)
