Git in PLD - basic HOWTO

Kacper Kornet draenog at pld-linux.org
Tue Jul 10 16:02:34 CEST 2012


On Tue, Jul 10, 2012 at 04:04:01PM +0200, Jakub Bogusz wrote:
> On Tue, Jul 10, 2012 at 03:40:58PM +0200, Kacper Kornet wrote:
> > On Tue, Jul 10, 2012 at 04:26:00PM +0300, Caleb Maclennan wrote:
> > > 2) Is there a way to set git's user.email config variable without
> > > doing it globally? I use git for other things where my pld nick is not
> > > my email. However with each package being a separate repository,
> > > setting it in the repository config file instead of the global one
> > > means having to set it in a couple thousand places. Is there a way to
> > > match the git origin server or some other way of marking that
> > > everything under rpm/packages gets a certain set of configuration
> > > values?

> > The solution that I know is to define a wrapper around git, that calls
> > call "git -c user.email=whatever", where whatever depends on the current
> > path. It's cumbersome, but maybe better then nothing.

> Is it possible to include user.* setting in per-package .git/config?

Yes there is.

> If so, slug.py or builder could set it based on some PLD-specific config
> file or environment variable.

It is already implemented in git-init, which is used during
initialization of repositories. Just set proper GIT_TEMPLATE_DIR.
See section "TEMPLATE DIRECTORY" in man git-init.

-- 
  Kacper


More information about the pld-devel-en mailing list