Re: Git-Mediawiki : cloning a set of pages
- From
Jeff King <peff@peff.net>
- Date
- Jun 8, 2011, 17:13 UTC
- Message-ID
- <20110608171338.GA3917@sigill.intra.peff.net>
- In-Reply-To
- <BANLkTim54YGYN50gZtqwe8w6-du_aTDWTQ@mail.gmail.com>
On Wed, Jun 08, 2011 at 07:04:27PM +0200, Sverre Rabbelier wrote:
Show 12 quoted lines
> On Wed, Jun 8, 2011 at 17:19, Jeff King <peff@peff.net> wrote: > > Maybe it would be even simpler and more flexible to give clone a "-c" > > flag that writes specific config variables in the newly-created > > repository. > > This makes a lot of sense. What about a use case like git-svn supports > currently, where you want to indicate "use the default > trunk/branches/tags setup"? Yes, you could do `git clone -c defaults > svn://example.com` and then git-remote-svn can set the relevant config > options itself. The only downside is that git-remote-svn then needs to > unset 'defaults' and set the appropriate values itself (to avoid > cluttering the config file). Thoughts?
Yeah, I'm not sure. There is a similar case in the mediawiki helper itself, too. If I say:
git clone -c mediawiki.pagesfiles /path/to/pages mediawiki::...
Should that add config that looks at /path/to/pages every time I fetch? Should it parse the pages file and load it into the config file as a set of config options? Should it copy the pages file into the .git directory and rewrite the config option to point to the local version?
So I think that while setting config options may be useful for some things, the right model for other things is more like a command-line option. Maybe we need to offer both forms.
-Peff