httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Yann Ylavic <>
Subject Re: Bug 57227 - Patch still not in main stream
Date Mon, 29 Feb 2016 14:55:54 GMT
[CCing the original bugs@ list and dev@ which I somehow added from my
first response.
Not sure bugs@ is to be addressed directly though, it is normally CCed
for bugzilla reports only...]

On Mon, Feb 29, 2016 at 2:52 PM, Bruno Raoult <> wrote:
>> On Mon, Feb 29, 2016 at 1:31 PM, Bruno Raoult <> wrote:
>> >
>> > I did find a bug in mod_autoindex more than one year ago, about missing
>> > CSS
>> > class, and proposed a patch at same time
>> > (
>> > It appears that this patch is still not applied in recent versions.
>> It seems that it was merge in version 2.4.12, with
>> (no changelog associated, though).
> It was indeed (just checked on my latest Ubuntu desktop, which has 2.4.12).
> In order to find out by myself next time, how did you jump from r1648201
> (which I
> found from my bug/patch report) to r1651644 and then to 2.4.12 ?
> I am missing some steps for sure.

I guess the easiest way would have been a CHANGES entry, and/or the
merge commit referenced in the bugzilla report (this is usually the
case, but not here...).
Personnaly I just searched r1648201 in my mailbox history which
pointed out to the merge in r1651644, but I'm subscribed to the cvs@
list (as a committer).

Otherwise I think the safest way is to search the trunk commit
reference (r1648201 here) either on google (something like "httpd
2.4.x merge r1648201", but it does not seem to help here) or better in
the commit messages of the 2.4.x branch (that is in the output of: svn
log -v,
which points to r1651644 here.
Not very friendly but it works since each commit in a stable branch
contains the reference of the original (merged) commit in trunk...

For the release number (here 2.4.12), I compared the date of the
commit r1651644 in 2.4.x (still given by the "svn log ..." command
above) with the ones of the releases (maintained in the STATUS file of
each branch, eg: svn cat,
2.4.12 being the next version released (2.4.11 wasn't) after "Wed, Jan
14 2015" (the date of r1651644).

Hope this helps :p

View raw message