Ag. D. Hatzimanikas wrote:
> On Κυρ, Μάρ 02, at 02:36 Bruce Dubbs wrote:
>> We might just want to place a link to the ticket in the changelog.
>>
> I asked for this months ago.
>
> Randy McMurchy wrote:
>> On Tue, Jul 31, at 01:21 [EMAIL PROTECTED] wrote:
>>>> + ... Fixes Trac ticket #2366.</para>
>>> Shall I add an entity in general.ent, as they do in LFS to make an
>>> actual link so to be "clickable" from the changelog entry?
>>> Like:
>>>
>>> <!ENTITY bfs-ticket-root "http://wiki.linuxfromscratch.org/bfs/ticket/";>
>>>
>> No, I would prefer not. In fact, I don't think we need to
>> identify that a Trac ticket is being fixed at all. To me
>> it would just be too much clutter having a URL in every
>> changelog entry.
>
> Neither I want to add a link to track when its just a normal
> package update; but in all other situations, yes, I find it
> quite useful.
>
> Maybe reconsider?
Could it be easily auto-generated in the html if we pick a specific
format? Ex: in the changelog source we have:
'{para}Fixed linker issue with libfoo. Ticket #9999{/para}'
When the html is generated, it turns 'Ticket #9999' into a link for us?
IMO, that would be pretty nice to have, even on package updates.
-- DJ Lucas
--
http://linuxfromscratch.org/mailman/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
