[apparmor] [patch 3/3] use capability rule class in aa.py and cleanprof.py
Steve Beattie
steve at nxnw.org
Wed Dec 3 20:24:18 UTC 2014
On Wed, Dec 03, 2014 at 07:19:11PM +0100, Christian Boltz wrote:
> The remaining question is if we want to split the commit to know who
> broke which part *g* or if we just commit the merged patch with two
> authors mentioned.
By passing multiple --author flags to bzr commit, we can list both
of us as the authors of the patches.
> Oh, and is one of us still allowed to send an Ack for a merged patch
> (which would mean acking partially self-written code), or do we need to
> force someone else to review it? ;-)
I suspect we're allowed to ACK each others' code. Since I've pushed
out the merged patches and listed myself as signing off on them,
there's pretty much an implicit ack on my side.
--
Steve Beattie
<sbeattie at ubuntu.com>
http://NxNW.org/~steve/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <https://lists.ubuntu.com/archives/apparmor/attachments/20141203/3e177da8/attachment.pgp>
More information about the AppArmor
mailing list