On Mon, 2004-02-02 at 23:17, Brad House wrote:
> > Tough, we all have 12 hour or close working days. As for calming down,
> > I _am_ calm - you have not seen me on the war path yet =) And I do not
> > imagine myself that the -r4 changes was not the only.
> > Also, 'resigning' from the livecd project because you overstep
> > boundaries with no visible regard for the impact or feelings of others,
> > is to be frank, silly. Ask me - any change that usually cannot wait a
> > few hours to be verified is usually a wrong one. I did this more than
> > once myself - overstepping boundaries for this 'critical' fix, and the
> > result was worse than what the few extra hours of waiting could ever
> > have done.
> > We do not ask your soul - we ask some sort of regard. Work with us,
> > and you will see that most of us will work with you.
> Seeing as I had already 'overstepped' my bounds as you put it and
> committed a -r4 in the first place (it was never anything you had
> committed), what was the harm at all in me updating my own ebuild?
I did not talk this time about -r4, I talked about the other commit.
> Anyhow, we use CVS for collaboration, etc, this send me a diff and I'll
> approve it thing is BS as long as we don't mess anything up, which I
> have taken steps to make sure I do not.
> Oh also, just as a little wood for your fire, I committed a patch to
> -r2,-r3,-r4, and -r5 that fixes a bug where /dev was not being created
> _again_. And I did view this as fairly critical, and it was simplistic.
If you want to get into it, then technically you 'fixed' it in the
wrong place. The real culprit in this situation (and others that might
pop up besides /dev if $ROOT != '/'), is keepdir_mount().
> We are a team, I don't believe ONE person should hold up bug fixes, etc
> when things are easily fixed without disturbance. I view myself as a
> competant developer, if I were not, perhaps it would be a different
> situation. Again, I bring up the point, why do we use CVS if not to
> collaborate ?
Ok, so please go and commit to portage and see where that gets you. As
far as I can see, the only 'team' in your vocabulary, is the one that
gets you your way. You obviously fail to see why it is that some core
packages have, lets call it 'supervising maintainers' - its to make sure
that all changes are regulated and will not break something due to
limited understanding from less active developers when it comes to that
Go and have a look at the kernel for instance. All major parts have
their respective maintainers who concur changes, and then send it off
to Linus. Same thing here.
The biggest issue here - or reason why I get 'my panties in a wad' - is
that you do not even have the decency to let me know about a change. I
never said I was the all mighty committer of baselayout - check the
ChangeLog .. others _do_ commit there ... _after_ they check with me.
Its not what you do, but _how_ you do it.
What you also seemingly seem to miss, is this is not about me getting my
undies tied up, but you repeatedly disregarding any type of system in
place, and doing as _you_ please. Yes, _you_. Great hey, its still all
about you - just get this ... its not in a good way?
So please, go get an ego adjustment; un-wad _your_ panties; and play
some ball. Just for the record - you did see that I did not CC releng?
I see I should apologise for underestimating your righteousness,
Gentoo Linux Developer, Desktop/System Team Developer
Cape Town, South Africa