From: Andreas Ericsson <ae@op5.se>
To: git@vger.kernel.org
Subject: Re: [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config
Date: Mon, 21 Nov 2005 17:34:47 +0100 [thread overview]
Message-ID: <4381F727.2090005@op5.se> (raw)
In-Reply-To: <Pine.LNX.4.63.0511211653420.2569@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
>
> What do people say? Is it useless to move that information into the
> config, where it can be queried/replaced/set/removed by the config "API",
You're thinking the wrong way around. "Is it useless so we should
refrain?" is not the same as "is it useful enough to do?".
> or should we continue with two incompatible ad-hoc formats? (If that
> sounds biased, it was not meant to be.)
>
I don't use Cogito myself so I'm not aware of what incompatibilities
there are. However, it's a user-friendliness layer, so it can choose to
do things differently if it wants to, but changing how the plumbing
works to match the porcelain seems wrong to me.
--
Andreas Ericsson andreas.ericsson@op5.se
OP5 AB www.op5.se
Tel: +46 8-230225 Fax: +46 8-230231
next prev parent reply other threads:[~2005-11-21 16:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-21 13:56 [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config Johannes Schindelin
2005-11-21 15:44 ` Josef Weidendorfer
2005-11-21 15:57 ` Johannes Schindelin
2005-11-21 16:25 ` Josef Weidendorfer
2005-11-21 16:34 ` Andreas Ericsson [this message]
2005-11-21 22:26 ` Junio C Hamano
2005-11-27 12:59 ` Petr Baudis
2005-11-28 1:52 ` Johannes Schindelin
2005-11-28 6:22 ` Junio C Hamano
2005-11-28 8:43 ` Andreas Ericsson
2005-11-28 9:14 ` Junio C Hamano
2005-11-28 12:59 ` Josef Weidendorfer
2005-11-28 13:11 ` Andreas Ericsson
2005-11-28 14:32 ` Generic configuration plumbing (Was: Re: [RFC 2/2] Automatically transform...) Josef Weidendorfer
2005-11-28 15:26 ` Johannes Schindelin
2005-11-28 13:48 ` [RFC 2/2] Automatically transform .git/{branches,remotes} into .git/config Petr Baudis
2005-11-28 15:03 ` Josef Weidendorfer
2005-11-29 6:04 ` Junio C Hamano
2005-11-28 16:29 ` Johannes Schindelin
2005-11-28 13:59 ` Petr Baudis
2005-11-28 16:33 ` Johannes Schindelin
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=4381F727.2090005@op5.se \
--to=ae@op5.se \
--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.