From: Adam Spiers <git@adamspiers.org>
To: Ramkumar Ramachandra <artagnon@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: Proposal: sharing .git/config
Date: Tue, 19 Feb 2013 14:38:43 +0000 [thread overview]
Message-ID: <CAOkDyE-at6jJZGV-3H4jEZhAsid41oqcQtEmad+5rwRhYiFUpQ@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0npW6TLdMNd5_zw-RAB0bjF9DDoyAVSx4Zx=7AmvdEo3w@mail.gmail.com>
On Tue, Feb 19, 2013 at 9:25 AM, Ramkumar Ramachandra
<artagnon@gmail.com> wrote:
> Hi,
>
> I have this itch where I want to share my remotes config between
> machines. In my fork, I should be able to specify where my upstream
> sources are, so remotes get set up automatically when I clone. There
> are also other things in .git/config that would be nice to share, like
> whether to do a --word-diff (why isn't it a configuration variable
> yet?) on the repository. The only problem is that I have no clue how
> to implement this: I'm currently thinking a special remote ref?
I handle these kinds of configuration tasks out of band using mr,
and it works pretty well:
https://github.com/aspiers/mr-config/#readme
https://github.com/aspiers/mr-config/blob/master/sh.d/git-remotes
Food for thought ...
prev parent reply other threads:[~2013-02-19 14:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 9:25 Proposal: sharing .git/config Ramkumar Ramachandra
2013-02-19 10:03 ` Thomas Rast
2013-02-19 10:24 ` Ramkumar Ramachandra
2013-02-19 10:39 ` Thomas Rast
2013-02-19 10:34 ` Duy Nguyen
2013-02-19 15:36 ` Jeff King
2013-03-11 19:31 ` Ramkumar Ramachandra
2013-03-12 8:53 ` Jeff King
2013-03-18 9:00 ` Ramkumar Ramachandra
2013-03-18 11:48 ` Jeff King
2013-02-19 14:38 ` Adam Spiers [this message]
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=CAOkDyE-at6jJZGV-3H4jEZhAsid41oqcQtEmad+5rwRhYiFUpQ@mail.gmail.com \
--to=git@adamspiers.org \
--cc=artagnon@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).