[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-scm-interest
Subject:    Re: [Kde-scm-interest] accountability
From:       Jeff Mitchell <mitchell () kde ! org>
Date:       2009-11-19 23:13:20
Message-ID: 4B05D110.3020906 () kde ! org
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


Thiago Macieira wrote:
> Em Quarta-feira 18. Novembro 2009, ās 12.58.15, Jeff Mitchell escreveu:
>> Thiago Macieira wrote:
>>> Em Quarta-feira 18. Novembro 2009, ās 07.31.50, Riccardo Iaconelli 
> escreveu:
>>>> Mmh... but this is a problem also with SVN, no?
>>> No. In SVN, if you commit, you're the author.
>> And in Git, if you merge someone else's code, you're the "author" too.
> 
> Well, no.
> 
> $ git log --pretty=fuller --committer=David\ Faure -n1 | cat
> commit 3cb304990f81799e6811b699b6b6ad1c32ec1107
> Author:     David Faure <faure@kde.org>
> AuthorDate: Fri May 29 16:36:15 2009 +0200
> Commit:     David Faure <faure@kde.org>
> CommitDate: Fri May 29 16:36:15 2009 +0200
> 
>     Fix compilation with -pedantic
> 
> This is Qt. David has no push rights.
> 
> Yet he's both author and committer. The question is: who introduced his commit 
> to Qt?
> 
> The repository is public. You have the SHA-1. The answer to my question then 
> is left as an exercise for the reader.

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.

--Jeff


["signature.asc" (application/pgp-signature)]

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


[prev in list] [next in list] [prev in thread] [next in thread]