1 |
On Sun, Jan 19, 2014 at 02:33:06AM +0100, Tom Wijsman wrote: |
2 |
> On Sat, 18 Jan 2014 15:24:59 -0800 |
3 |
> "W. Trevor King" <wking@×××××××.us> wrote: |
4 |
> > If it doesn't need to get updated, then it probably already |
5 |
> > started out explaining the consensus ;). |
6 |
> |
7 |
> That is a guess, you can look this up in past patches. |
8 |
|
9 |
Sure. Will you? If I want to touch some code, and it looks |
10 |
confusing, I'll use blame to see who wrote it and whay they were |
11 |
thinking about. If the commit message is not informative, I usually |
12 |
give up. I have a hard time imaging folks tracking down the thread |
13 |
that spawned that patch, assuming such a thread even exists, for each |
14 |
troublesome line they'd like to touch. It's much easier to summarize |
15 |
any issues the list resolved (because they're likely the same |
16 |
questions the new dev is asking) in the commit message, where future |
17 |
developers can find them. |
18 |
|
19 |
> > You spend time if you want to spend time and add whoever you feel |
20 |
> > moved to add. |
21 |
> |
22 |
> We discuss whether to make it policy to add involved people. |
23 |
|
24 |
But “involved” can be hard to pin down, especially by someone who may |
25 |
be applying v5 of a patch that hasn't been carefully following the |
26 |
whole discussion in earlier versions. The Linux kernel docs say [1]: |
27 |
|
28 |
If this patch fixes a problem reported by somebody else, consider |
29 |
adding a Reported-by: tag to credit the reporter for their |
30 |
contribution. |
31 |
|
32 |
Note the “consider” wiggle word. They are a bit more formal about |
33 |
Reviewed-by, but only because it's signing off on their Reviewer's |
34 |
statement of oversight. In general, if you're not signing some |
35 |
statement with the tag, formalizing “involved” is hard. |
36 |
|
37 |
> > If you are submitting v2 of a patch, and feel a desire |
38 |
> > to credit reviewers / testers with this syntax, I think that's |
39 |
> > considerate of you. If you are committing someone else's patch to |
40 |
> > master, and want to record the folks who acked it on the list to |
41 |
> > distribute responsibility, that's fine too. If you want to use |
42 |
> > another syntax, or not do any of this at all, it's still fine by me |
43 |
> > ;). However, if a consistent syntax already exists, I see no reason |
44 |
> > not to use it when it suits your purpose. |
45 |
> |
46 |
> We discuss here whether to make it policy to use the same syntax. |
47 |
|
48 |
I don't understand the distinction between “here are some guidelines, |
49 |
apply as and if you see fit” and “make it a policy to …”. Say you |
50 |
have a situation like this: |
51 |
|
52 |
1. Alice submits a bug-report to bugs.g.o. |
53 |
2. Bob codes up a Portage patch and sends it to the list. |
54 |
3. Charlie responds to Bob's patch on the list with "Reviewed-by". |
55 |
4. Dan responds to Bob's patch on the list with "Reviewed-by", and |
56 |
asks for any opposition. |
57 |
|
58 |
… time passes, and nobody speaks up … |
59 |
|
60 |
5. Dan applies Bob's patch to the master branch, but neglects: |
61 |
|
62 |
Submitted-by: Alice <a@×××××××.net> |
63 |
Reviewed-by: Charlie <c@×××××××.net> |
64 |
Reviewed-by: Dan <d@×××××××.net> |
65 |
|
66 |
6. ? |
67 |
|
68 |
As I understand it, 6 should be: |
69 |
|
70 |
6a. Everyone gets on with their lives. |
71 |
|
72 |
I could see a situation where: |
73 |
|
74 |
6b. Charlie reminds Dan that he could have used the tags. Everyone |
75 |
gets on with their lives. |
76 |
|
77 |
Is there another alternative step 6 implied by the “policy” keyword? |
78 |
Or is the policy workflow even more different somehow? |
79 |
|
80 |
Cheers, |
81 |
Trevor |
82 |
|
83 |
[1]: https://www.kernel.org/doc/Documentation/SubmittingPatches |
84 |
|
85 |
-- |
86 |
This email may be signed or encrypted with GnuPG (http://www.gnupg.org). |
87 |
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy |