From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH 3/3] fetch: optionally store the current remote information in the config
Date: Sun, 30 Apr 2006 18:07:01 +0200 [thread overview]
Message-ID: <e32n9j$ibl$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.63.0604301749130.3641@wbgn013.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> On Sun, 30 Apr 2006, Jakub Narebski wrote:
>
>> P.S. I wonder if it would be difficult to implement 'include <file>' for
>> config file...
>
> You really need that?
Need? Not exactly. I don't think git ever reach complexity of Apache or
Samba configuration files, and _need_ for includes. Still dividing separate
areas of configuration (core, user, default commands options, remotes) has
it's merits.
--
Jakub Narebski
Warsaw, Poland
next prev parent reply other threads:[~2006-04-30 16:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-30 13:24 [PATCH 3/3] fetch: optionally store the current remote information in the config Johannes Schindelin
2006-04-30 14:19 ` Jakub Narebski
2006-04-30 15:52 ` Johannes Schindelin
2006-04-30 16:07 ` Jakub Narebski [this message]
[not found] ` <20060430103046.35c1385f.seanlkml@sympatico.ca>
2006-04-30 14:30 ` sean
2006-04-30 15:49 ` Johannes Schindelin
[not found] ` <20060430123709.11fcdd5f.seanlkml@sympatico.ca>
2006-04-30 16:37 ` sean
2006-04-30 16:51 ` Jakub Narebski
[not found] ` <20060430131936.43598f6f.seanlkml@sympatico.ca>
2006-04-30 17:19 ` sean
2006-04-30 17:35 ` Jakub Narebski
2006-04-30 17:09 ` Johannes Schindelin
[not found] ` <20060430132819.3af8e9d1.seanlkml@sympatico.ca>
2006-04-30 17:28 ` sean
2006-04-30 22:21 ` Junio C Hamano
2006-05-02 8:59 ` Junio C Hamano
2006-05-02 12:42 ` Johannes Schindelin
2006-05-03 0:36 ` Junio C Hamano
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='e32n9j$ibl$1@sea.gmane.org' \
--to=jnareb@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).