--===============0962452601==
Content-Type: multipart/signed;
  boundary="nextPart33128894.TRnuU1hcK3";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart33128894.TRnuU1hcK3
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

> I don't have the ability to look at this now -- but my understanding was
> that when you performed a merge and the merge commit was created, the
> author of that merge commit was the person who performed the merge.
> Unless I'm wrong about that, that was my point -- the person who merged
> someone else's code is the "author" of that merge, and could be
>  accountable.
That would be true, but merge commits don't happen for fast-forward merges=
=20
(where no real merging is involved), which can happen quite easily if cherr=
y-
picking or rebasing is used, or if the repository isn't moving very fast. S=
o=20
that, unfortunately, can't be relied on.
=2D-=20
=2DComputerDruid

--nextPart33128894.TRnuU1hcK3
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.11 (GNU/Linux)

iEYEABECAAYFAksF0vQACgkQhP2Vm0oJTtztwACeMLvzCRuA71O/Nx3M9SRprpZ+
hdEAnR9qgyBd3TlFMO5rPcfWqlXf7C7F
=mf0X
-----END PGP SIGNATURE-----

--nextPart33128894.TRnuU1hcK3--

--===============0962452601==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest

--===============0962452601==--