Charles Plessy writes:
> I had similar thoughts when preparing the patch, but did not propose the
> merge as I did not find an easy way to produce with DebianDoc-SGML a
> stand-alone text version of the upgrade checklist, which I think has
> some value. My gut feeling is that it may be doable wi
Le Sun, Feb 26, 2012 at 04:39:59PM -0800, Russ Allbery a écrit :
>
> I thought about this more this morning, and realized that the real
> solution to all of this is to make the upgrading checklist an appendix to
> Policy. That way, we can use regular internal document links and let the
> document
Charles Plessy writes:
> Le Sun, Dec 25, 2011 at 09:58:37AM -0800, Russ Allbery a écrit :
>> My first inclination would be to change the debian-policy package to
>> stop generating the broken-down version of the upgrading-checklist that
>> has multiple HTML files (there doesn't seem to be much po
Le Sun, Dec 25, 2011 at 09:58:37AM -0800, Russ Allbery a écrit :
>
> My first inclination would be to change the debian-policy package to stop
> generating the broken-down version of the upgrading-checklist that has
> multiple HTML files (there doesn't seem to be much point for that
> document), g
Charles Plessy writes:
> Le Sun, Dec 25, 2011 at 09:58:37AM -0800, Russ Allbery a écrit :
>> Charles Plessy writes:
>>> Using IDs, like this:
>>
>>>Version 3.9.3.0
>>
>>> The HTML document will have anchors like that:
>>
>>> 2.1 Version 3.9.3.0
>>
>>> They will be easy to preserve if t
Le Sun, Dec 25, 2011 at 09:58:37AM -0800, Russ Allbery a écrit :
> Charles Plessy writes:
>
> > Using IDs, like this:
>
> >Version 3.9.3.0
>
> > The HTML document will have anchors like that:
>
> > 2.1 Version 3.9.3.0
>
> > They will be easy to preserve if the checklist migrates to DocB
Charles Plessy writes:
> Le Sun, Sep 04, 2011 at 09:13:14AM +0200, Raphael Hertzog a écrit :
>> On Sat, 03 Sep 2011, Giovanni Mascellani wrote:
>>> I though about this, but couldn't come up with any easy solution. I
>>> mostly consider this tool to be useful for people who just have to
>>> check
Le Sun, Sep 04, 2011 at 09:13:14AM +0200, Raphael Hertzog a écrit :
>
> On Sat, 03 Sep 2011, Giovanni Mascellani wrote:
> > I though about this, but couldn't come up with any easy solution. I
> > mostly consider this tool to be useful for people who just have to check
> > the very last versions of
Hi,
On Sat, 03 Sep 2011, Giovanni Mascellani wrote:
> I though about this, but couldn't come up with any easy solution. I
> mostly consider this tool to be useful for people who just have to check
> the very last versions of the policy, so the problem is actually quite
> mitigated.
>
> I don't ev
Hi.
On 03/09/2011 14:40, Bill Allombert wrote:
> Hello Giovanni,
>
> upgrading-checklist really points to sections of a specific version of policy
> and not the current one, except for the first entries. How do you plan to
> handle that ? When policy is restuctured, links will get wrong.
I thou
On Mon, Aug 29, 2011 at 09:45:52AM +0200, Giovanni Mascellani wrote:
> Package: debian-policy
> Severity: wishlist
>
> Hi.
>
> It would be useful to have a copy of the HTML version of
> upgrading-checklist somewhere on the web. This could, for example, be
> linked from the PTS when some package's
Package: debian-policy
Severity: wishlist
Hi.
It would be useful to have a copy of the HTML version of
upgrading-checklist somewhere on the web. This could, for example, be
linked from the PTS when some package's Standards-Version has to be
upgraded.
In #485085 the problem of the links from upgr
12 matches
Mail list logo
