1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA256 |
3 |
|
4 |
On 03/12/13 11:21, Sebastian Luther wrote: |
5 |
> The problem with all these variables is that we don't maintain |
6 |
> them. If they disappear, change meaning or new ones are added we |
7 |
> constantly have to fix our documentation. |
8 |
I don't think this is a problem. I could fix any documentation bugs |
9 |
related to this. |
10 |
|
11 |
> The python team's documentation [1] is just fine imo. Maybe this |
12 |
> one needs to be more user visible? Maybe by linking it into the |
13 |
> handbook (if it isn't already)? |
14 |
It could be linked in the man page of make.conf as well. |
15 |
|
16 |
|
17 |
Ultimately my stance is that it should be in the man page. I can add |
18 |
them myself. However, I will leave it out if more people agree with |
19 |
Sebastian than me. |
20 |
- -- |
21 |
Alexander |
22 |
alexander@××××××.net |
23 |
http://plaimi.net/~alexander |
24 |
-----BEGIN PGP SIGNATURE----- |
25 |
Version: GnuPG v2.0.22 (GNU/Linux) |
26 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
27 |
|
28 |
iF4EAREIAAYFAlKdtd4ACgkQRtClrXBQc7WwpgD+IYfhSD43rRpU4NTUaBRpWzyB |
29 |
vZcUJveJttZEd5MlUF8A+gLKqf9T9EtzjQzqTWl2twuUu/oDSwhPe9fePM4ZrEg2 |
30 |
=bbW5 |
31 |
-----END PGP SIGNATURE----- |