Re: What's cooking in git.git (Sep 2011, #06; Wed, 21)

From: Junio C Hamano <gitster@pobox.com>
Date: Sep 22, 2011, 23:12 UTC
Message-ID: <7v4o04xjcb.fsf@alter.siamese.dyndns.org>
In-Reply-To: <m3r538qj0j.fsf@localhost.localdomain>

Jakub Narebski <jnareb@gmail.com> writes:

Show 12 quoted lines

> Junio C Hamano <gitster@pobox.com> writes:
>
>> --------------------------------------------------
>> [New Topics]
>  
>> * jc/namespace-doc-with-old-asciidoc (2011-09-16) 1 commit
>>  - Documentation/gitnamespaces.txt: cater to older asciidoc
>
> I'll need this to e.g. test the "rpm" target after adding
> Documentation/gitweb.txt and Documentation/gitweb.conf.txt
>
> But it is not something very urgent...

Now I am confused. If you apply your patch on top of "master" then you cannot create "rpm" on your platform, not because your patch is busted, but because "master" lacks the documentation fix from that topic. Is that what you mean?

If the reason the documentation fix for "master" is needed is because a new feature scheduled for the upcoming release has broken documentation, then wouldn't we need the fix before the release, whether you are working on your patch or not? How can it be not urgent if that is the case?

On my boxes with recent Debian, Ubuntu, and F14, I am not suffering from the lack of the workaround, but if distros need the workaround, then the time to apply it is now, not post release.

Hmmm....