> Best practice is to use a proper revision control system (one which
> can do patch stack management if that's desired) and generate a
> consolidated .dsc/.diff.gz for people who don't want to get to grips
> with it.
Which will only give useful results if we have a central repository
for all pac
On Tue, Dec 18, 2007 at 08:05:54PM +, Ian Jackson wrote:
> Russ Allbery writes ("Re: Task list for a policy release"):
> > #379150: Documentation for Breaks in dpkg
> > This support was added in dpkg 1.14.6, so I'm inclined to accept and
> > commit this patch. I trust Ian to document the feat
Russ Allbery writes ("Re: Task list for a policy release"):
> #379150: Documentation for Breaks in dpkg
>
> This support was added in dpkg 1.14.6, so I'm inclined to accept and
> commit this patch. I trust Ian to document the feature, and the wording
> seems fine to me. The only caveat is that I
3 matches
Mail list logo
