I've noticed this a few times now.
The change below was originally pushed by me to master:
------ cut here-----
Commit a16880742e06cca261f98a06fba476e273d79ed0:
Makes more sense to keep personal details together so each uid appears
once only. The uid data can later be expanded if necessary
Branch: refs/heads/master
Author: Sebb <[email protected]>
Committer: Sebb <[email protected]>
Pusher: sebb <[email protected]>
------------------------------------------------------------
www/roster/public_ldap_committers.rb | +++++ -----
------------------------------------------------------------
69 changes: 34 additions, 35 deletions.
------------------------------------------------------------
diff --git a/www/roster/public_ldap_committers.rb
b/www/roster/public_ldap_committers.rb
index e039fda..da9401a 100644
--- a/www/roster/public_ldap_committers.rb
+++ b/www/roster/public_ldap_committers.rb
------ cut here-----
So why do we now get a duplicate message attributing the change to you?
The same has happened in the reverse, i.e. sometimes I end up
apparenty repeating a change you made.
Is there perhaps a process we could follow to avoid this confusing duplication?
On 24 January 2016 at 19:47, Sam Ruby <[email protected]> wrote:
> Commit 79f4989be128c2d56e4520e185e4f59e3e390c6f:
> Merge branch 'master' of github.com:apache/whimsy
>
>
> Branch: refs/heads/master
> Author: Sam Ruby <[email protected]>
> Committer: Sam Ruby <[email protected]>
> Pusher: rubys <[email protected]>
>
> ------------------------------------------------------------
> www/roster/public_ldap_committers.rb | +++++ -----
> ------------------------------------------------------------
> 69 changes: 34 additions, 35 deletions.
> ------------------------------------------------------------
>
>
> diff --git a/www/roster/public_ldap_committers.rb
> b/www/roster/public_ldap_committers.rb
> index e039fda..da9401a 100644
> --- a/www/roster/public_ldap_committers.rb
> +++ b/www/roster/public_ldap_committers.rb
<snip>
