All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Nathan W. Panike" <nathan.panike@gmail.com>
To: git@vger.kernel.org
Subject: [PATCH 0/2] Create a shared config file
Date: Sat, 27 Nov 2010 09:00:41 -0600	[thread overview]
Message-ID: <cover.1290870041.git.nathan.panike@gmail.com> (raw)

Configuration should normally be on a per-repository or per-user basis.  There
are cases where it would be helpful to have a project share configuration
across repositories and between developers.  Normally this happens only via
e-mail or IRC or by word-of-mouth.  The solution implemented by these patches
is to have a .gitconfig file in the toplevel of the repository.

This is not a finished implementation, as I have no tests written.  Instead,
this is ``one way to do it.''

Nathan W. Panike (2):
  Add support for a shared config file
  Document toplevel .gitconfig file

 Documentation/config.txt |   11 ++++++++++
 builtin/config.c         |    9 +++++++-
 config.c                 |   49 +++++++++++++++++++++++++++++++++++++++++++++-
 3 files changed, 67 insertions(+), 2 deletions(-)

-- 
1.7.3.2.347.gd33a62

             reply	other threads:[~2010-11-27 15:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-27 15:00 Nathan W. Panike [this message]
2010-11-25 17:21 ` [PATCH 1/2] Add support for a shared config file Nathan W. Panike
2010-11-27 16:29   ` Thiago Farina
2010-11-25 20:01 ` [PATCH 2/2] Document toplevel gitconfig file Nathan W. Panike
2010-11-27 15:52   ` Jonathan Nieder
2010-11-27 16:04 ` [PATCH 0/2] Create a shared config file Nguyen Thai Ngoc Duy

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=cover.1290870041.git.nathan.panike@gmail.com \
    --to=nathan.panike@gmail.com \
    --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.