Re: linux-next: Signed-off-by missing for commits in the bpf-next tree

From: Bart Van Assche
Date: Wed Dec 12 2018 - 18:45:27 EST

On Wed, 2018-12-12 at 15:39 -0800, Alexei Starovoitov wrote:
+AD4 On Thu, Dec 13, 2018 at 09:48:20AM +-1100, Stephen Rothwell wrote:
+AD4 +AD4 Hi Alexei,
+AD4 +AD4
+AD4 +AD4 On Wed, 12 Dec 2018 12:53:11 -0800 Alexei Starovoitov wrote:
+AD4 +AD4 +AD4
+AD4 +AD4 +AD4 On Thu, Dec 13, 2018 at 07:32:45AM +-1100, Stephen Rothwell wrote:
+AD4 +AD4 +AD4 +AD4 Hi all,
+AD4 +AD4 +AD4 +AD4
+AD4 +AD4 +AD4 +AD4 Commits
+AD4 +AD4 +AD4 +AD4
+AD4 +AD4 +AD4 +AD4 3bdc28aa2340 (+ACI-selftests/bpf: add btf annotations for cgroup+AF8-local+AF8-storage maps+ACI)
+AD4 +AD4 +AD4 +AD4 1dfd1959fed4 (+ACI-bpf: add bpffs pretty print for cgroup local storage maps+ACI)
+AD4 +AD4 +AD4 +AD4 3adc62d9a5be (+ACI-bpf: pass struct btf pointer to the map+AF8-check+AF8-btf() callback+ACI)
+AD4 +AD4 +AD4 +AD4 9cf3a785dc4c (+ACI-selftests/bpf: use +AF8AXw-bpf+AF8-constant+AF8-htons in test+AF8-prog.c+ACI)
+AD4 +AD4 +AD4 +AD4
+AD4 +AD4 +AD4 +AD4 are missing a Signed-off-by from their committers.
+AD4 +AD4 +AD4
+AD4 +AD4 +AD4 the must be a script mistake?
+AD4 +AD4 +AD4
+AD4 +AD4 +AD4 I clearly see SOBs for all of them.
+AD4 +AD4
+AD4 +AD4 For example:
+AD4 +AD4
+AD4 +AD4 commit 3bdc28aa2340bf1e5af753287b373522bd1c02a9 (bpf-next/master)
+AD4 +AD4 Author: Roman Gushchin
+AD4 +AD4 Date: Mon Dec 10 15:43:02 2018 -0800
+AD4 +AD4
+AD4 +AD4 selftests/bpf: add btf annotations for cgroup+AF8-local+AF8-storage maps
+AD4 +AD4
+AD4 +AD4 Add btf annotations to cgroup local storage maps (per-cpu and shared)
+AD4 +AD4 in the network packet counting example.
+AD4 +AD4
+AD4 +AD4 Signed-off-by: Roman Gushchin
+AD4 +AD4 Cc: Alexei Starovoitov
+AD4 +AD4 Cc: Daniel Borkmann
+AD4 +AD4 Acked-by: Martin KaFai Lau
+AD4 +AD4 Signed-off-by: Daniel Borkmann
+AD4 +AD4
+AD4 +AD4 But it was committed by you, not Daniel.
+AD4 since there were only 4 commits I fixed them up manually.
+AD4 But this approach doesn't scale.
+AD4 We do rebase our trees when we need to fixup or drop patches and
+AD4 at any given point a number of commits will be committed by me
+AD4 and another set by Daniel. When we rebase we cannot keep adding
+AD4 our SOBs to the other person SOBs.
+AD4 Then comes the next rebase and we get to the point of
+AD4 double and triple SOBs ?
+AD4 I think you need to adjust the script to something like:
+AD4 SOBs by Daniel +AHw Alexei +AD0APQ commit by Daniel +AHw Alexei
+AD4 in bpf and bpf-next trees.

Are you aware of Linus' opinion about rebasing? If not, please have a look
at or