1 |
On Tue, 21 Jan 2014 09:20:04 -0800 |
2 |
"W. Trevor King" <wking@×××××××.us> wrote: |
3 |
|
4 |
> On Tue, Jan 21, 2014 at 05:59:54PM +0100, Tom Wijsman wrote: |
5 |
> > On Tue, 21 Jan 2014 08:51:14 -0800 W. Trevor King wrote: |
6 |
> > > On Tue, Jan 21, 2014 at 04:40:19PM +0100, Tom Wijsman wrote: |
7 |
> > > > On Sun, 19 Jan 2014 18:32:35 -0800 W. Trevor King wrote: |
8 |
> > > > > No policy/suggestion/goal is going to be followed 100% of the |
9 |
> > > > > time. |
10 |
> > > > |
11 |
> > > > This way, it seems preferable to use the mailing list when |
12 |
> > > > blaming. |
13 |
> > > |
14 |
> > > Unless some of the discussion happened on IRC. There are several |
15 |
> > > possible channels for patch discussion, but only one commit |
16 |
> > > message per patch. |
17 |
> > |
18 |
> > Exactly, without knowledge codification all that will continue to be |
19 |
> > a "feel like", "probably not", "shouldn't", "unless some". |
20 |
> |
21 |
> I don't see that as a problem. I guess I just have more faith that |
22 |
> current devs will put in a reasonable best-effort without codification |
23 |
> beyond “here are some conventions you may want to use”, and that |
24 |
> future devs will be competent enough to still be productive in the |
25 |
> face of unhelpful commit messages. |
26 |
|
27 |
If they are just mentioned at random all the time, perhaps half of them |
28 |
get remembered or so; the half of what is remembered gets given through |
29 |
to the next generation of future devs, this up to the point that it |
30 |
would have been a better idea to write this down than to have faith. |
31 |
|
32 |
It is a competence that's far from becoming a core competence that way. |
33 |
|
34 |
-- |
35 |
With kind regards, |
36 |
|
37 |
Tom Wijsman (TomWij) |
38 |
Gentoo Developer |
39 |
|
40 |
E-mail address : TomWij@g.o |
41 |
GPG Public Key : 6D34E57D |
42 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |