| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA256 |
| 3 |
|
| 4 |
On 16/01/14 22:18, Tom Wijsman wrote: |
| 5 |
> My plan is to first work a bit on repoman to get to know it, then |
| 6 |
> when knowing better where everything is work on refactoring it. |
| 7 |
That, along with "I'll use this ugly short cut, but only this one |
| 8 |
time!", is what they all say. Plans change. Things happen. |
| 9 |
|
| 10 |
> If I start to refactor right away, or start adding random files |
| 11 |
> without knowing where everything is; I would create a more broken |
| 12 |
> design than it is. |
| 13 |
Yes. Please think before you start hammering your keyboard. The keyboard |
| 14 |
is just a means to an end. |
| 15 |
|
| 16 |
> Don't worry, I plan on a fully refactored Portage as well as good |
| 17 |
> practices when adding new checks; which will definitely become |
| 18 |
> necessary as we go forward. |
| 19 |
We have to worry. Because, as mentioned, plans change; things happen. |
| 20 |
|
| 21 |
|
| 22 |
Please do not push this patch. And please do not carry on with this |
| 23 |
mentality of "yes, I know what I am doing is wrong, but I'll fix it |
| 24 |
eventually, some day, I promise." |
| 25 |
- -- |
| 26 |
Alexander |
| 27 |
alexander@××××××.net |
| 28 |
http://plaimi.net/~alexander |
| 29 |
-----BEGIN PGP SIGNATURE----- |
| 30 |
Version: GnuPG v2.0.22 (GNU/Linux) |
| 31 |
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/ |
| 32 |
|
| 33 |
iF4EAREIAAYFAlLYTd4ACgkQRtClrXBQc7VNmQD+KhIxhOAC4/IPB4hn+ugL1NIH |
| 34 |
zNtPtTObzBMIivybstQBAISvE55N7Gb7hh6os+pZcvVilVqhhQP/V3b1RIk9tC2j |
| 35 |
=0lAa |
| 36 |
-----END PGP SIGNATURE----- |
Archives