Re: svn commit: r1769900 - /httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en

[Marion & Christophe JAILLET]

Hi,

why removing compatibility note (i.e. 2.4.7) ?

CJ


Le 15/11/2016 à 23:57, elu...@apache.org a écrit :

Author: elukey
Date: Tue Nov 15 22:57:36 2016
New Revision: 1769900

URL: http://svn.apache.org/viewvc?rev=1769900=rev
Log:
documentation rebuild

Modified:
 httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en

Modified: httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en
URL: 
http://svn.apache.org/viewvc/httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en?rev=1769900=1769899=1769900=diff
==
--- httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en (original)
+++ httpd/httpd/trunk/docs/manual/mod/mod_headers.html.en Tue Nov 15 22:57:36 
2016
@@ -309,8 +309,16 @@ available in 2.4.10 and later
  
  setifempty

  The request header is set, but only if there is no previous header
-with this name.
-Available in 2.4.7 and later.
+with this name.
+
+The Content-Type header is a special use case since there might be
+the chance that its value have been determined but the header is not part
+of the response when setifempty is evaluated.
+It is safer to use set for this use case like in the
+following example:
+Header set Content-Type "text/plain" "expr=-z 
%{CONTENT_TYPE}"
+
+
  
  unset

  The response header of this name is removed, if it exists.

Re: Query on linking Apache Mailing list with GitHUub Commits

[William A Rowe Jr]

More importantly, the commit message for those lines modified should credit
the original submitter(s)... Who may or may not even be committers to this
project.

On Nov 15, 2016 17:21, "Eric Covener"  wrote:

> On Tue, Nov 15, 2016 at 11:18 AM, Mehvish.Rashid 
> wrote:
> > Am assuming that commit on the file means only that person has worked on
> the
> > code. Is it possible that more than one person is working on the code
> before
> > one single commit? How can I know how many people worked on a code file
> > before the commit?
>
> "svn blame" on a file will tell you who has touched each line.  svn
> log will tell you similar.  An archive of c...@httpd.apache.org would
> tell you the same in more free-form way.
>

Re: Query on linking Apache Mailing list with GitHUub Commits

[Eric Covener]

On Tue, Nov 15, 2016 at 11:18 AM, Mehvish.Rashid  wrote:
> Am assuming that commit on the file means only that person has worked on the
> code. Is it possible that more than one person is working on the code before
> one single commit? How can I know how many people worked on a code file
> before the commit?

"svn blame" on a file will tell you who has touched each line.  svn
log will tell you similar.  An archive of c...@httpd.apache.org would
tell you the same in more free-form way.

RE: Query on linking Apache Mailing list with GitHUub Commits

[Mehvish . Rashid]

Am assuming that commit on the file means only that person has worked on the 
code. Is it possible that more than one person is working on the code before 
one single commit? How can I know how many people worked on a code file before 
the commit?



From: Yehuda Katz [mailto:yeh...@ymkatz.net]
Sent: 15 November 2016 03:18
To: dev@httpd.apache.org
Subject: Re: Query on linking Apache Mailing list with GitHUub Commits

HTTPD uses SVN, Github is just a nice mirror.

Each git commit should have a line that starts "git-svn-id". The SVN commit 
number and canonical link is there.

- Y

On Mon, Nov 14, 2016 at 8:45 PM, Mehvish.Rashid 
> wrote:
I see code commits on this link: https://github.com/apache/httpd/commits
But when I search for a svn commit, for example, "Re: svn commit: r1768245 - " 
from mailing list: 
https://lists.apache.org/list.html?dev@httpd.apache.org:2016-11 on the above 
link I cannot find it. Am looking for a way to link the committers in svn and 
mails sent by them on the above mailing list.

-Original Message-
From: Eric Covener [mailto:cove...@gmail.com]
Sent: 15 November 2016 01:06
To: Apache HTTP Server Development List
Subject: Re: Query on linking Apache Mailing list with GitHUub Commits

On Mon, Nov 14, 2016 at 7:58 PM, Mehvish.Rashid 
> wrote:
> 1) I would like to know where do developers on Apache HTTP Server ask 
> questions relating to code in inactive file.
> Inactive file is a file on which there are no commit for some duration. When 
> some developer starts to work on the code of such file where do they ask 
> questions.
> I see some communication on this link:
> https://lists.apache.org/list.html?dev@httpd.apache.org
> Are there any other places to find answers relevant to code.

That's the right list, there are no other options.  modules-dev@ is for module 
development questions about modules that aren't a part of httpd.

> 2) Can questions on mailing list in the above link be linked to
> commits on: https://github.com/apache/httpd

Anyone is free to send an email with a link to a github link, but they are more 
likely to address something in terms of its SVN revision or respond to the 
email generated during the commit.  For httpd, github is just a read/only 
mirror.

--
Eric Covener
cove...@gmail.com

Re: ap_get_status_line(int)

[Stefan Eissing]

Great!

> Am 15.11.2016 um 10:09 schrieb Yann Ylavic :
> 
> On Fri, Nov 4, 2016 at 5:51 PM, Stefan Eissing
>  wrote:
>> 
>> The patch looks fine to me. I do just feel a tad bit uncomfortable with the
>> empty description. How about
>> +return apr_psprintf(p, "%i No Description", status);
>> 
>> There are probably tons of client implementations out there that will fail
>> when nothing comes after the space.
> 
> Good point, committed in r1769760 with: apr_psprintf(p, "%i Status
> %i", status, status).
> 
> Regards,
> Yann.

apreq release

[Issac Goldstand]

Hi all,

Someone (finally) noticed that apreq's test suite isn't compatible with
Apache 2.4 and requested a change.  Given that we haven't released an
updated apreq in nearly 6 years, I'm inclined to make/test the changes
to the test suite and immediately go to a release cycle.

Does anyone want time to add anything else to libapreq-2.14 before I
start tarring and voting (in the next few days, I hope)?

Re: ap_get_status_line(int)

[Yann Ylavic]

On Fri, Nov 4, 2016 at 5:51 PM, Stefan Eissing
 wrote:
>
> The patch looks fine to me. I do just feel a tad bit uncomfortable with the
> empty description. How about
> +return apr_psprintf(p, "%i No Description", status);
>
> There are probably tons of client implementations out there that will fail
> when nothing comes after the space.

Good point, committed in r1769760 with: apr_psprintf(p, "%i Status
%i", status, status).

Regards,
Yann.