Re: git bikeshedding (Re: triggers in dpkg, and dpkg maintenance)
On Sun, 02 Mar 2008, Robert Collins wrote:
> On Sun, 2008-03-02 at 02:09 -0300, Henrique de Moraes Holschuh wrote:
> > And I am completely *sure* it would not be irrelevant for me were I
> > debugging dpkg without a full, complete, dpkg-regular-developer level of
> > understanding of the code. Or if I were trying to understand how dpkg
> > works, so as to start working on dpkg, for that matter.
> Well, when I sat down some years back to do a couple of things with
> dpkg; I found no need to consult change logs to understand the current
> code of the time. Perhaps its quality has massively decreased since; yet
> somehow I doubt that.
That's certainly good to hear, it means the barrier for new developers is
low, which is quite good. The same would hold for debugging?
"One disk to rule them all, One disk to find them. One disk to bring
them all and in the darkness grind them. In the Land of Redmond
where the shadows lie." -- The Silicon Valley Tarot