public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox•net>
To: "Post, Mark K" <mark.post@eds•com>
Cc: "Linus Torvalds" <torvalds@osdl•org>, git@vger•kernel.org
Subject: Re: Git-daemon messing up permissions for gitweb
Date: Fri, 09 Jun 2006 14:06:22 -0700	[thread overview]
Message-ID: <7virnam435.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <5A14AF34CFF8AD44A44891F7C9FF410507957896@usahm236.amer.corp.eds.com> (Mark K. Post's message of "Fri, 9 Jun 2006 16:52:22 -0400")

"Post, Mark K" <mark.post@eds•com> writes:

> Since umask isn't an environment variable, per se, I'm not sure how this
> will change anything.

I do not configure my sshd, so you may need a bit more reading
on it yourself; $HOME/.ssh/environment does not seem to be it,
as you said.

> One other thing I noticed is that init-db.c spells core.sharedRepository
> with a capital R, but setup.c spells it "core.sharedrepository" with no
> upper case letters.  Would this make any difference to anything I'm
> seeing? 

The distinction should not matter since the code downcases
(git_config_set_multivar() in config.c) it, but to avoid future
confusion we might want to downcase the one in init-db.c

  reply	other threads:[~2006-06-09 21:06 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-09 20:52 Git-daemon messing up permissions for gitweb Post, Mark K
2006-06-09 21:06 ` Junio C Hamano [this message]
2006-06-10  0:35   ` [PATCH/RFC] Retire SIMPLE_*** stuff Junio C Hamano
2006-06-10 14:13     ` [PATCH] Built-in git-get-tar-commit-id (was: [PATCH/RFC] Retire SIMPLE_*** stuff.) Rene Scharfe
2006-06-10  0:39   ` [PATCH] shared repository settings enhancement Junio C Hamano
2006-06-10  0:46     ` Linus Torvalds
2006-06-10  1:38       ` Jakub Narebski
2006-06-10  3:49       ` Junio C Hamano
2006-06-10  4:08         ` Linus Torvalds
2006-06-10  4:19           ` Junio C Hamano
2006-06-10  4:39             ` Linus Torvalds
2006-06-10 21:30 ` Git-daemon messing up permissions for gitweb Alex Riesen
2006-06-10 21:41   ` Linus Torvalds
2006-06-10 22:30     ` Alex Riesen
  -- strict thread matches above, loose matches on Subject: below --
2006-06-09 20:45 Post, Mark K
2006-06-09 20:29 Post, Mark K
2006-06-09 20:08 Post, Mark K
2006-06-09 20:18 ` Junio C Hamano
2006-06-09 20:22 ` Linus Torvalds
2006-06-09 20:34   ` Junio C Hamano
2006-06-09 20:44     ` Linus Torvalds
2006-06-09 21:02       ` Jakub Narebski
2006-06-09 19:11 Post, Mark K
2006-06-09 19:27 ` Jakub Narebski
2006-06-09 18:41 Post, Mark K
2006-06-09 18:58 ` Jakub Narebski
2006-06-09 19:05 ` Linus Torvalds
2006-06-09 20:01   ` Junio C Hamano
2006-06-09 19:51 ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7virnam435.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox$(echo .)net \
    --cc=git@vger$(echo .)kernel.org \
    --cc=mark.post@eds$(echo .)com \
    --cc=torvalds@osdl$(echo .)org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox