{"thread":{"id":"32058","subject":"http-backend GIT_COMMITTER_NAME & -EMAIL documentation bug","startedAt":"2012-11-10T15:26:19Z","lastAt":"2012-11-10T15:26:19Z","messageCount":1,"participants":["gima@iki.fi"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"202757","messageId":"509E721B.8070700@iki.fi","threadId":"32058","inReplyTo":null,"subject":"http-backend GIT_COMMITTER_NAME & -EMAIL documentation bug","fromName":"","fromEmail":"gima@iki.fi","sentAt":"2012-11-10T15:26:19Z","receivedAt":"2012-11-10T15:26:19Z","isPatch":false,"sender":{"key":"gima@iki.fi","avatar":null},"body":"Documentation says that envvars GIT_COMMITTER_NAME and \nGIT_COMMITTER_EMAIL formed from REMOTE_USER and REMOTE_ADDR, but doesn't \nmention that they are left alone if they have been set already.\nReferring to: \nhttps://github.com/git/git/blob/master/Documentation/git-http-backend.txt#L178\n\nSource code says that they are set conditionally (referring to this part \nof the source):\nhttps://github.com/git/git/blob/master/http-backend.c#L335\n\nAnd the (most recent) commit pertaining to this behavior explains the \nchange:\nhttps://github.com/git/git/commit/e32a4581bcbf1cf43cd5069a0d19df07542d612a\n\nI'm also for the possibility of custom implementations assigning those \nenvvars, so could the documentation be changed to reflect that?\n"}]}