1 |
On Sat, Jul 10, 2010 at 12:13, Enrico Weigelt <weigelt@×××××.de> wrote: |
2 |
> I've already explained the strategy behind the git repo (and not |
3 |
> doing plaintext patches). Please refer to my paper, and my other |
4 |
> mails posted recently on this list. |
5 |
|
6 |
I'm not quite sure I understand your response here. He didn't ask for |
7 |
you to explain the strategy. He asked for you to provide plain-text |
8 |
patches. |
9 |
|
10 |
I think a point has been made pretty clear at this point: they need |
11 |
plain-text patches. Requiring developers to learn an entirely new |
12 |
work-flow just to get your patches into the tree is time-consuming and |
13 |
bothersome, at the least. This isn't a discussion about whether or not |
14 |
your system is better. It's about how best to integrate your work into |
15 |
Gentoo. |
16 |
|
17 |
The developers have decided the best way is through plain-text |
18 |
patches. That's really all there is to it. Take it or leave it. |
19 |
|
20 |
The discussion about how best to join multiple branches of development |
21 |
across the open-source world together really does not belong in this |
22 |
thread, as far as I can tell. |
23 |
|
24 |
-- |
25 |
Jacob |
26 |
|
27 |
"For then there will be great distress, unequaled |
28 |
from the beginning of the world until now — and never |
29 |
to be equaled again. If those days had not been cut |
30 |
short, no one would survive, but for the sake of the |
31 |
elect those days will be shortened." |
32 |
|
33 |
Are you ready? |