22:38:36 <AI0867> shadowm: we discussed moving wesnoth to git at wescamp (again)
22:40:50 <shadowm> AI0867: at github?
22:41:23 <shadowm> what was the outcome?
22:44:01 <AI0867> everyone present thought git was superior to svn
22:44:29 <AI0867> we asked zookeeper for his opinion and he was mostly opposed (mainly because of not knowing it)
22:44:46 <AI0867> main question would be where to go
22:44:48 <shadowm> That's been his position for years, but has anyone actually considered mine?
22:44:52 <AI0867> bugtracker integration
22:45:12 <AI0867> artist stuff?
22:45:12 <shadowm> That is, I have stated my position in #wesnoth-dev at least thrice.
22:45:21 <shadowm> No, artists don't use svn even.
22:45:25 <AI0867> I may have missed or forgotten it
22:45:41 <AI0867> ease of use?
22:46:07 <shadowm> Will there be a ML discussion?
22:46:08 <shadowm> I don't want to go into details atm, but it boils down to repository size.
22:46:15 <AI0867> ah, that
22:46:28 <AI0867> it's not going to be much bigger than an svn checkout
22:46:34 <AI0867> which is already huge, true
22:46:40 <AI0867> there should be
22:46:49 <AI0867> but nobody has bothered summarizing everything yet
22:46:50 <shadowm> Yes, but you can do non-recursive SVN checkouts
22:47:06 <AI0867> from my (very limited) experience, tortoisegit is a port of the interface and workflow of tortoisesvn
22:47:06 <shadowm> you can avoid downloading music that way, for example
22:47:21 <AI0867> you *can* do that with git, but not easily
22:47:34 <shadowm> and I'm not really sure where this "it's not going to be much bigger than a svn checkout" argument comes from, frankly
22:48:04 <shadowm> when doing a svn checkout you download the HEAD snapsshot for the selected subtree (when recursive)
22:48:18 <shadowm> that should be about the size of the release tarball
22:48:39 <AI0867> no
22:48:42 <AI0867> it's twice the size
22:48:51 <shadowm> I am talking about download sizes
22:48:54 <AI0867> that is, you get a copy of HEAD to compare locally
22:48:55 <shadowm> *not* storage size
22:48:59 <AI0867> ah
22:49:38 <shadowm> shadowm@reicore:~/src/wesnoth$ du -sh .git/objects
22:49:38 <shadowm> 1.7G    .git/objects
22:50:23 <AI0867> you can still get a shallow clone though
22:50:32 <shadowm> if I had to download that back in the day, I'd not have been able to do much
22:50:33 <AI0867> that should be equivalent in size to an svn checkout
22:50:47 <shadowm> (in fact, I'd be unable to download that right now too)
22:51:21 <shadowm> a shallow clone is substantially less useful from what I've heard
22:52:05 <shadowm> "A shallow repository has a number of limitations (you cannot clone or fetch from it, nor push from nor into it), but is adequate if you are only interested in the recent history of a large project with a long history, and would want to send in fixes as patches."
22:52:26 <shadowm> notice it says "nor push from nor into it"
22:52:51 <shadowm> given Wesnoth's current development model, the lack of pushing would inconvenience some people
22:53:17 <shadowm> more generally, it's annoying that git doesn't have a way to resume a clone operation
22:53:24 <AI0867> I was going to suggest partial downloads, but my largest pack is 1.2 GiB
22:53:57 <AI0867> yeah, that is a problem