On Wed, Jun 08, 2011 at 01:19:38PM +0200, Claire Fousse wrote: > The problem is not the feature in itself but the way you call it. > Just so you remember, here is the command to clone the mediawiki : > git clone mediawiki::http://yourwiki.com > > As it is now, git clone does not implement a way to define a set of pages. > The 2 solutions we think of are : > * git clone mediawiki::http://yourwiki.com$$page1$$page2 ... > Where $$ is a separator still to be determined. It should not be > something which could appear in the title of a page. > It is a simple way to proceed but it becomes horrible when you want > to clone many pages. Ick, yeah, that is kind of ugly. I think this is a general problem with the clone and remote helper interface that we are going to need to solve. It seems like clone should allow transport-specific options to pass through the command line and make it to the transport. Something like: git clone -c option=value mediawiki::http://... where the "option" is up to the transport to interpret. It could be implemented as a set of in-core options that get passed to the remote helper over the pipe. But that leaves the helper with probably having to store the options for future runs. 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. Like: git clone -c mediawiki.page=page1 \ -c mediawiki.page=page2 \ http://... Then the remote helper can just consult the git config. As a bonus, it also lets you do things like: git clone -c core.ignorecase=true git://... which is currently awkward (you either have to have set such variable in your ~/.gitconfig, or you must use init+config+fetch to do a clone manually. Getting back to mediawiki, that gives us a slightly nicer syntax, but we're still specifying each page on the command line (and now it's even more verbose!). I would think two things could help: 1. Some kind of globbing, like mediawiki.page="foo_*". The usefulness of this will depend on how well pages in the wiki are named, though. 2. Have a config option to point to a file containing page entries, one per line. > * write a git-mw-clone script which asks the user to enter a set > of pages and may store this set of titles in the git config. > This script should then call git-clone which will call the > remote-mediawiki functions. git-mw-clone would clone the entire > wiki and git-mw-clone --pages would ask the user to enter their > set. The problem here is that a not git-like command is > required. Yeah, I like this less because you lose a lot of the seamlessness of the remote helper solution. -Peff -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html