On Tue, Aug 14, 2007 at 06:47:20AM -0700, Arjan van de Ven wrote:
>
> On Tue, 2007-08-14 at 10:20 +0100, Alan Cox wrote:
> > > MODULE_MAINTAINER() was discussed a while ago but embedding information
> > > into
> > > the binary has the problem you can't ever change deployed systems,
> > > meaning
> > > it lags by design. If a maintainer changes, people would still be using
> > > the
> > > information from their old binaries, meaning a replaced maintainer might
> > > get
> > > contacted for potentially years still (and the new one not).
> >
> > And as was pointed out at the time, the people whining about that were
> > talking out of the wrong equipment. The supplier of the code can no more
> > or less easily change the binary as the matching source tree once its been
> > shipped. In fact its probably easier to change the binaries as the
> > sources will be left on CD.
> >
> > The only non-stale source is git-blame.
>
> the other angle is this: if someone becomes the new maintainer, does he
> really want to "maintain" all the really old versions of the code out
> there that predate him, or does he only want to go forward?
>...
What about cases like maintainers using company email addresses and
changing company?
E.g. Jens is still block layer maintainer but the @suse address he used
for years suddenly no longer existed after he left Suse.
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
