The trick was using svn switch:
svn checkout http://svn.wikimedia.org/svnroot/mediawiki/trunk/phase3
cd phase3
svn switch http://svn.wikimedia.org/svnroot/mediawiki/trunk/extensions
extensions/ --depth immediates
cd extensions/
svn checkout
On 07/10/11 23:13, Arthur Richards wrote:
Thanks for bringing this up Tomasz - I meant to send a reply about this
earlier this week but it fell off my radar.
For those that don't know, the Wikimedia repo holds WMF-related resources
that are not directly MediaWiki related. The fundraising team
Maybe it [Wikimedia] could be the first one to migrate to git ? It seems
easier to
Normally I'd be into this, but I'm nervous about the timing. As I understand
it, the conversion is set to begin in November, which is when the fundraiser
will be starting. Using a repo that is predominantly
On Tue, Oct 11, 2011 at 10:48 AM, Arthur Richards
aricha...@wikimedia.org wrote:
Skimming over the plan on the wiki page, I don't see anything about a
contingency or failsafe plan, which is something I'd really like to know!
Just go back to using SVN :)
Thanks for bringing this up Tomasz - I meant to send a reply about this
earlier this week but it fell off my radar.
For those that don't know, the Wikimedia repo holds WMF-related resources
that are not directly MediaWiki related. The fundraising team and
fundraising analytics relies on this repo
We also want to move over the generic Wikimedia repot.
--tomasz
On Wed, Oct 5, 2011 at 7:41 AM, Rob Lanphier ro...@wikimedia.org wrote:
On Tue, Oct 4, 2011 at 9:21 AM, Merlijn van Deen valhall...@arctus.nl wrote:
Currently, svn.wikimedia.org also hosts other repositories, most notably the
On Tue, Oct 4, 2011 at 9:21 AM, Merlijn van Deen valhall...@arctus.nl wrote:
Currently, svn.wikimedia.org also hosts other repositories, most notably the
pywikipedia repository. Is the plan to keep svn.wikimedia.org and svn-based
code
review online after the switch, or will the pywikipedia
On 24 September 2011 00:49, Platonides platoni...@gmail.com wrote:
Daniel Friesen wrote:
Does svn actually update disconnected svn directories that just happen
to be in a subdirectory? If it does do that then I do admit we might
want to provide a handy script to batch upgrade... well, actually
On 24/09/11 09:22, Niklas Laxström wrote:
rm -rf extensions
svn co . extensions
svn status should now show S extensions and you have all
extensions. If you don't want them all, use --depth empty and svn up
them individually.
We really need to have this tip somewhere on
Niklas Laxström wrote:
On 24 September 2011 00:49, Platonides wrote:
Daniel Friesen wrote:
Does svn actually update disconnected svn directories that just happen
to be in a subdirectory? If it does do that then I do admit we might
want to provide a handy script to batch upgrade... well,
On 23/09/11 01:06, Rob Lanphier wrote:
There has been resistance to this in the past, and there still may be
some resistance.
Resistance is futile. All your base are belong to us.
--
Ashar Voultoiz , sorry could not resist.
___
Wikitech-l mailing
There is no scary git future. A future with SVN, now that's scary
On 9/22/11 10:22 PM, Alolita Sharma wrote:
This is awesome. Seconding Trevor on our move to git +∞**
Brion - thanks for jumping in to do our-scary-git-future session as a repeat
at tech days :-)
Alolita
On Thu,
Alolita Sharma alolita.sha...@gmail.com writes:
This is awesome. Seconding Trevor on our move to git +∞**
+100!
This is great news.
Congrats for this ongoing effort, and good luck for the move :)
--
Bastien
___
Wikitech-l mailing list
Has the svn:externals problem been solved?
What flow would need to follow people currently using sparse checkouts.
There have been patches in git ml for sparse clones, but they hadn't
been applied, last time I checked.
___
Wikitech-l mailing list
On Fri, Sep 23, 2011 at 12:14 PM, Platonides platoni...@gmail.com wrote:
Has the svn:externals problem been solved?
What flow would need to follow people currently using sparse checkouts.
There have been patches in git ml for sparse clones, but they hadn't
been applied, last time I checked.
On Fri, Sep 23, 2011 at 1:06 AM, Rob Lanphier ro...@wikimedia.org wrote:
* Code review tool: barring unforeseen complications, we're planning
to use Gerrit. We need to make sure it'll be a suitable replacement
for our existing tool
I've talked to some of the ops folks a bit, and we've
On 23/09/11 10:39, Max Semenik wrote:
snip
Another thing: I currently use SVN's trick with embedded checkouts where the
content of /extensions in a trunk/phase3 checkout is replaced with a
checkout of trunk/extensions. This way, extensions are located at the
canonical path relative to core and
I've talked to some of the ops folks a bit, and we've already agreed
that inline display of diffs is something we really need to add to
Gerrit. I've filed a feature request to this end:
http://code.google.com/p/gerrit/issues/detail?id=1137
It's worth pointing out that Google Code will let
I've talked to some of the ops folks a bit, and we've already agreed
that inline display of diffs is something we really need to add to
Gerrit. I've filed a feature request to this end:
http://code.google.com/p/gerrit/issues/detail?id=1137
It's worth pointing out that Google Code will let
On 11-09-23 09:51 AM, Ashar Voultoiz wrote:
On 23/09/11 10:39, Max Semenik wrote:
snip
Another thing: I currently use SVN's trick with embedded checkouts where the
content of /extensions in a trunk/phase3 checkout is replaced with a
checkout of trunk/extensions. This way, extensions are
Daniel Friesen wrote:
Does svn actually update disconnected svn directories that just happen
to be in a subdirectory? If it does do that then I do admit we might
want to provide a handy script to batch upgrade... well, actually
extension wise I've been thinking of that for extensions for
Hi everyone,
For a long time, we've been talking about migrating from Subversion to
Git. It's time to start getting more serious about it.
First: the need to do this. There is pretty broad acceptance that we
should move to a distributed version control system (DVCS). Our
current
+∞**
This is not going to be easy, but nothing worth doing ever is. I've been
using git for personal projects for a while, and would agree that the issues
that have come about are more to do with learning than regret.
- Trevor
On Thu, Sep 22, 2011 at 4:06 PM, Rob Lanphier ro...@wikimedia.org
Yay!
I've volunteered to do a quick intro-to-our-scary-git-future session at the
New Orleans hackathon; I'll see if I can lay out a nice workflow
demonstration from a few different perspectives:
* staff or very active volunteer developer who's doing a lot of core or
high-priority extension work
On Thu, Sep 22, 2011 at 6:29 PM, Brion Vibber br...@pobox.com wrote:
Yay!
I've volunteered to do a quick intro-to-our-scary-git-future session at the
New Orleans hackathon; I'll see if I can lay out a nice workflow
demonstration from a few different perspectives:
* staff or very active
This is awesome. Seconding Trevor on our move to git +∞**
Brion - thanks for jumping in to do our-scary-git-future session as a repeat
at tech days :-)
Alolita
On Thu, Sep 22, 2011 at 6:41 PM, Ryan Lane rlan...@gmail.com wrote:
On Thu, Sep 22, 2011 at 6:29 PM, Brion Vibber
26 matches
Mail list logo
