All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christian Senkowski <csenkowski@gmx.de>
To: git@vger.kernel.org
Subject: How to share config and hooks ?
Date: Wed, 27 May 2009 21:58:04 +0200	[thread overview]
Message-ID: <4A1D9B4C.7030504@gmx.de> (raw)

[-- Attachment #1: Type: text/plain, Size: 600 bytes --]

I am searching for a way to share 'config' and hooks/* automatically.
I'd like to change and commit them as normal files and every user
cloning this repo should get those.

One way might be a little wrapper-script for git-clone which looks if
repo/.gitconfig or repo/.githooks exist and copies then the files to
repo/.git/[...]

But I am searching for a way to do this without any additional scripts.

Does anyone have an idea ?
And what'd you say about implementing this (with a
yes-please-copy-the-found-files/no-leave-them-alone - question) directly
into the git-binary ?


-- 


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 280 bytes --]

             reply	other threads:[~2009-05-27 20:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-27 19:58 Christian Senkowski [this message]
2009-05-27 20:11 ` How to share config and hooks ? Johannes Schindelin
2009-05-28  5:54 ` David Aguilar

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=4A1D9B4C.7030504@gmx.de \
    --to=csenkowski@gmx.de \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.