Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo

This is an OpenPGP/MIME signed message (RFC 4880 and 3156) --qdO8bPbfeBvH4dk92FKmuEDkVrmFePAW2 Content-Type: multipart/mixed; boundary="dHFxNqgcPKvcesCMcwN6aVOtxx1dXIGD3" From: =?UTF-8?B?TWFyYyBEZXF1w6huZXMgKER1Y2sp?= <duck(a)redhat.com&gt; To: infra(a)ovirt.org Message-ID: <b39c9ab0-91f2-6726-eece-543a26efec26(a)redhat.com&gt; Subject: Re: [JIRA] (OVIRT-696) create an 'infra-ansible' repo References: <JIRA.18604.1471435113000(a)Atlassian.JIRA&gt; <JIRA.18604.1471435113707(a)ovirt-jira.atlassian.net&gt; <JIRA.18604.1471435113000.26.1471435200131(a)Atlassian.JIRA&gt; <1cdb68d9-ad05-a192-0f7a-5a418e37bfca(a)redhat.com&gt; In-Reply-To: <1cdb68d9-ad05-a192-0f7a-5a418e37bfca(a)redhat.com&gt; --dHFxNqgcPKvcesCMcwN6aVOtxx1dXIGD3 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: quoted-printable So cleanup done. In fact the commit hook added them when doing the git am :-/. So, when working on a topic branch, people usually intend to work on the same feature, so to stakup improvements and fixes on the same "patchset". I fail to see how to do that with git review and the current commit hook, as it does not seem to care about handling a branch as a series of patches in the same patchset. Are we supposed to handle the Change-ID manually? Please help on this matter, the conflicting docs on Internet did not really help. --dHFxNqgcPKvcesCMcwN6aVOtxx1dXIGD3-- --qdO8bPbfeBvH4dk92FKmuEDkVrmFePAW2 Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" --qdO8bPbfeBvH4dk92FKmuEDkVrmFePAW2--