1 |
On Wed, Nov 30, 2016 at 09:23:56PM +0000, Andrey Utkin wrote: |
2 |
> The difference between my submission and final variant by Matthew is big |
3 |
> in number of lines, but is trivial in content as you can see below, so I |
4 |
> don't believe that Matthew has written his variant from scratch on his |
5 |
> own (he hasn't given any note on tickets on bugs.g.o or github), it |
6 |
> seems more like intentional swapping and amending original lines |
7 |
> retaining identical outcome. |
8 |
> |
9 |
> Not that authorship of one or two commits is so crucial for me, or that |
10 |
> I'm the most ambitious wannabe-contributor. Hell, there's not much of |
11 |
> code at all in the ebuild - it's trivial; but also not much is needed |
12 |
> here to give credit. I have contributed to quite some FOSS projects, and |
13 |
> have run into theft of my patches a couple of times, and it never was by |
14 |
> pure accident. |
15 |
|
16 |
Though I wasn't involved in these commits, I have seen how easy and |
17 |
accidental it is to lose authorship information on a commit. That being |
18 |
said, finding where to draw the line on authorship can be difficult. |
19 |
|
20 |
I'm not sure how many others are aware of this, but I'll mention it just |
21 |
in case: provided it's done before pushing commits, the commit metadata |
22 |
and message can be amended locally with |
23 |
|
24 |
git commit --amend --author="Joe Smith <jsmith@×××××××.blah>" |
25 |
|
26 |
This will update the Author tag but leave the Committer tag untouched |
27 |
(and will allow fixing any problems with the commit message itself). |
28 |
Amending commits that are not the tip of your local clone will probably |
29 |
need an interactive rebase though (but I could be wrong about that). |
30 |
|
31 |
-- |
32 |
Sam Jorna (wraeth) |
33 |
GPG ID: 0xD6180C26 |