1 |
Alec Warner wrote: |
2 |
> Please don't commit files to profiles/ unless it has been discussed previously |
3 |
> on this ML. I don't care if your file is insignificant or 'won't affect |
4 |
> anything else' or that it's 'completely necessary'. Please discuss it first. |
5 |
> |
6 |
> You don't have to ask for a vote on it, or make everyone agree with you. You |
7 |
> don't even need to wait three weeks to make sure everyone read your mail. |
8 |
> This is definately one of those times where the apache lazy concensus works. |
9 |
> |
10 |
> "Hi I'm adding this file to profiles/ for reason X in three days if no one has |
11 |
> any issues with it." |
12 |
> |
13 |
> Thats really all I'd like to see. Something documented...So when I find the |
14 |
> file magically in profiles/ a week later I can be like "Oh, that was due to |
15 |
> mail on -dev" and not be like "hmm who did that" and then cvs log the file |
16 |
> and then have to hunt you down on irc to figure out why it's there. |
17 |
> |
18 |
> Courtesy towards fellow developers, especially when commiting to global spaces |
19 |
> such as profiles/ is appreciated by all. |
20 |
|
21 |
If you want to see something documented, shouldn't any reasonable commit |
22 |
message be enough? It's much easier to track that down using cvs log |
23 |
than trying to hunt down a random message on -dev, IMHO, because it's |
24 |
more closely tied to the actual change. |
25 |
|
26 |
I'm not really seeing this as a courtesy issue. The whole tree is a |
27 |
global space. |
28 |
|
29 |
Then again, I'm missing context because people have this weird thing |
30 |
about abstractly bringing up issues without discussing the actual problem. |
31 |
|
32 |
Thanks, |
33 |
Donnie |