From: Claire Fousse <claire.fousse@ensimag.imag.fr>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org, Sylvain Boulme <Sylvain.Boulme@imag.fr>,
Matthieu Moy <Matthieu.Moy@grenoble-inp.fr>,
Jeff King <peff@peff.net>,
srabbelier@gmail.com
Subject: Re: Git-Mediawiki : cloning a set of pages
Date: Thu, 9 Jun 2011 11:06:16 +0200 [thread overview]
Message-ID: <BANLkTin3eEJfXfB7aadxue-QMduimvh-tg@mail.gmail.com> (raw)
In-Reply-To: <m3lixcdz67.fsf@localhost.localdomain>
>> 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.
> [...]
>
> Well, what you need to do is to implement API for partial _clone_ (we
> have some SPI for partial checkout, but that is slightly different
> beast).
>
> Currently we have --depth=<n> to limit depth of history when cloning,
> and "git remote add -t <branch>" (repeated if necessary) to consider
> only a subset of branches, though unfortunately not in "git clone"
> yet.
>
> Not what you wanted to hear, I guess... :-(
Yes, not really what I wanted to hear, but I had the feeling it would
go this way =).
Our school project ends tomorrow, so starting tomorrow we will have less time
to work on this.
We chose to implement the first solution with ##:
git clone mediawiki::http://yourwiki.com##page1##page2..
This way that feature can be used for now, and It will be really
simple to change the
command later.
--
Claire Fousse
Grenoble INP - Ensimag
2A Télécommunication
claire.fousse@ensimag.imag.fr
prev parent reply other threads:[~2011-06-09 9:06 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-08 11:19 Git-Mediawiki : cloning a set of pages Claire Fousse
2011-06-08 15:19 ` Jeff King
2011-06-08 17:04 ` Sverre Rabbelier
2011-06-08 17:13 ` Jeff King
2011-06-09 15:50 ` Jeff King
2011-06-09 15:51 ` [PATCH 01/10] strbuf_split: add a max parameter Jeff King
2011-06-13 17:30 ` Junio C Hamano
2011-06-13 19:20 ` Jeff King
2011-06-09 15:51 ` [PATCH 02/10] fix "git -c" parsing of values with equals signs Jeff King
2011-06-09 15:52 ` [PATCH 03/10] config: die on error in command-line config Jeff King
2011-06-09 15:52 ` [PATCH 04/10] config: avoid segfault when parsing " Jeff King
2011-06-13 17:30 ` Junio C Hamano
2011-06-13 19:22 ` Jeff King
2011-06-09 15:54 ` [PATCH 05/10] strbuf: allow strbuf_split to work on non-strbufs Jeff King
2011-06-09 15:55 ` [PATCH 06/10] config: use strbuf_split_str instead of a temporary strbuf Jeff King
2011-06-09 15:55 ` [PATCH 07/10] parse-options: add OPT_STRING_LIST helper Jeff King
2011-06-09 15:55 ` [PATCH 08/10] remote: use new OPT_STRING_LIST Jeff King
2011-06-09 15:56 ` [PATCH 09/10] config: make git_config_parse_parameter a public function Jeff King
2011-06-09 15:57 ` [PATCH 10/10] clone: accept config options on the command line Jeff King
2011-06-09 17:10 ` Bert Wesarg
2011-06-09 17:12 ` Jeff King
2011-06-09 20:56 ` Jeff King
2011-06-09 22:34 ` Matthieu Moy
2011-06-08 17:14 ` Git-Mediawiki : cloning a set of pages Jakub Narebski
2011-06-09 9:06 ` Claire Fousse [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=BANLkTin3eEJfXfB7aadxue-QMduimvh-tg@mail.gmail.com \
--to=claire.fousse@ensimag.imag.fr \
--cc=Matthieu.Moy@grenoble-inp.fr \
--cc=Sylvain.Boulme@imag.fr \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=peff@peff.net \
--cc=srabbelier@gmail.com \
/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).