On Wed, May 04, 2011 at 11:51:44AM +0200, Arkadiusz Miskiewicz wrote: > On Wednesday 04 of May 2011, Kacper Kornet wrote: > > On Wed, May 04, 2011 at 11:37:16AM +0200, Arkadiusz Miskiewicz wrote: > > > On Tuesday 03 of May 2011, Kacper Kornet wrote: > > > > What is the reason that GIT_ variables are copied by ssh to remote > > > > session? I mean the following line in our default /etc/ssh/ssh_config.
> > > > AcceptEnv LANG LC_* LANGUAGE TZ GIT_* > > > To avoid a need to set all that on each remote system. > > > > I have just discovered that it break at least one feature in gitolite. > > > And the bug is where? > > The creation of wildcard repositories > > http://sitaramc.github.com/gitolite/doc/wildcard-repositories.html > > does not work. I can patch gitolite for it. But there is a small chance > > the patch would be accepted upstream. > How so? gitolite doesn't accept patches that fix bugs? See gitolite-mkdir.patch in PLD cvs. I have submitted it to the author of gitolte, and I have got answer: > It is my understanding that a standard git install comes with a hooks > template directory. You'll have to tell me how and why you ended up > with an empty hooks template directory. > > As a general rule, I don't accept patches for odd-ball or non-standard > configurations. You would not believe some of the things people > expect gitolite to solve for them :-) And I have a feeling that PLD ssh configuration would be said to be: "odd-ball or non-standard". -- Kacper _______________________________________________ pld-devel-en mailing list pld-devel-en@lists.pld-linux.org http://lists.pld-linux.org/mailman/listinfo/pld-devel-en