Matt Zimmerman <[EMAIL PROTECTED]> writes:
> Since testing is changing all the time, it would probably not be
> worthwhile to try to keep such a document up-to-date. Once woody
> cools and solidifies, someone could read through the complete set of
> Debian changelogs and try to pick out the most s
Matt Zimmerman <[EMAIL PROTECTED]> writes:
> Since testing is changing all the time, it would probably not be
> worthwhile to try to keep such a document up-to-date. Once woody
> cools and solidifies, someone could read through the complete set of
> Debian changelogs and try to pick out the most
On Thu, Jul 12, 2001 at 10:36:17AM +0200, Sebastien Chaumat wrote:
> Is there a kind of global changelog that explain the most significant diff
> between stable and testing (a kind of digest)?
>
> The interest would be to allow new maintainers (who weren't following the
> developpement fr
On Thu, Jul 12, 2001 at 10:36:17AM +0200, Sebastien Chaumat wrote:
> Is there a kind of global changelog that explain the most significant diff
> between stable and testing (a kind of digest)?
>
> The interest would be to allow new maintainers (who weren't following the
> developpement f
Hi,
Is there a kind of global changelog that explain the most significant
diff between stable and testing (a kind of digest)?
The interest would be to allow new maintainers (who weren't following
the developpement from the last release of stable) to avoid spending too
much time discovering
Hi,
Is there a kind of global changelog that explain the most significant
diff between stable and testing (a kind of digest)?
The interest would be to allow new maintainers (who weren't following
the developpement from the last release of stable) to avoid spending too
much time discoverin
6 matches
Mail list logo
