On 11-10-06 10:43 PM, Victor Vasiliev wrote:
On Wed, Oct 5, 2011 at 5:33 AM, Brion Vibber
<brion(a)pobox.com> wrote:
You can check out extensions as separate
repositories directly into
subfolders within core's 'extensions' dir for a ready-to-run system. But,
you *do* need to do either manually or scripted iteration over them to pull
updates or commit across repos. Git's submodules might be a useful way to
help automate checkouts, but they introduce their own complications for
maintenance.
That does not sound like The Bright Git Future.
--vvv
;) No, "The Bright Git Future" is when I can commit from my server,
pull
the changes to my local working copy, and push them to the central repo
from there. Since I develop on my servers, but don't trust them with my
private keys.
I currently do this with absolute hacks involving ssh up on both working
copies, piping svn diff through ssh into patch, commit, then another svn
up. The fact I have unfinished code lying around in my working copies
just makes things even more fun (I always make use of git's lovely index
which lets me pick piece by piece what parts of the diff to actually
commit). Not to mention that the svn diff trick has issues if I have a
new file.
This of course leads to lovely commits like:
This:
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/96668
And this:
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/96273
Humorous ones like this:
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/97180
^_^ And this kind of lovely commit:
https://www.mediawiki.org/wiki/Special:Code/MediaWiki/85242
By the way, when we switch to get I'll finally be able to get rid of
half the reason I make some commits without bothering to test them ;).
Since it will no longer be a huge hassle to make the change in a place I
can actually test it.
~Daniel Friesen (Dantman, Nadir-Seen-Fire) [
http://daniel.friesen.name]