From: David Miller <davem@davemloft.net>
To: alexei.starovoitov@gmail.com
Cc: sfr@canb.auug.org.au, daniel@iogearbox.net, ast@kernel.org,
netdev@vger.kernel.org, linux-next@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: linux-next: Signed-off-by missing for commits in the bpf-next tree
Date: Wed, 12 Dec 2018 16:45:26 -0800 (PST) [thread overview]
Message-ID: <20181212.164526.189502766995329983.davem@davemloft.net> (raw)
In-Reply-To: <20181212233909.hhf5q4vpi3mmi37u@ast-mbp.dhcp.thefacebook.com>
From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
Date: Wed, 12 Dec 2018 15:39:10 -0800
> But this approach doesn't scale.
> We do rebase our trees when we need to fixup or drop patches and
> at any given point a number of commits will be committed by me
> and another set by Daniel. When we rebase we cannot keep adding
> our SOBs to the other person SOBs.
> Then comes the next rebase and we get to the point of
> double and triple SOBs ?
If you use "--signoff" in whatever commands do the rebase you will
get exactly one signoff for yourself and Daniel at maximum. If it
is there already, git will not add a duplicate one on top.
next prev parent reply other threads:[~2018-12-13 0:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-12 20:32 linux-next: Signed-off-by missing for commits in the bpf-next tree Stephen Rothwell
2018-12-12 20:53 ` Alexei Starovoitov
2018-12-12 22:48 ` Stephen Rothwell
2018-12-12 23:39 ` Alexei Starovoitov
2018-12-12 23:45 ` Bart Van Assche
2018-12-13 0:20 ` Alexei Starovoitov
2018-12-13 0:45 ` David Miller [this message]
2018-12-13 4:33 ` Alexei Starovoitov
2018-12-13 5:37 ` Stephen Rothwell
2018-12-13 5:45 ` Alexei Starovoitov
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=20181212.164526.189502766995329983.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=alexei.starovoitov@gmail.com \
--cc=ast@kernel.org \
--cc=daniel@iogearbox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
/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).