3 ms·
I don't think they view that as a significant growth vector. Skimming an existing market is rarely a good tactic. Plus it's up to the developer. We can't have
by 1qaz2wsx3edc 13y ago
I don't think they view that as a significant growth vector. Skimming an existing market is rarely a good tactic.
Plus it's up to the developer. We can't have one-click-do-all buttons for everything.
- adamnemecek 13y agoWell if you want someone to do something, you should make it as easy as possible. Therefore, if you want someone to migrate their repo to your site, you should make it as easy as possible for them to do so.
- plorkyeran 13y agoEven if there's no one-click option, it'd be nice if the API exposed a much more flexible set of issue editing options to make it possible for us to write better importers ourselves.
- asveikau 13y agoIf only they had access to some kind of command line tool which lets you bulk pull and push and merge histories. Do you think they have something like that at github? :-)
- recursive 13y agoThere is a command line tool, unfortunately it's not very usable.
- claudius 13y agoI don’t think the GP was talking about ed scripts.
- asveikau 13y agoThey say you shouldn't explain your own jokes. My comment was that github is built around a tool that makes it really easy and efficient to import and merge histories. Namely git. It's amusing that the value-add portion of github, the web bits, suffer from problems like this, that a tool like git could conceivably be applied to.
- claudius 13y agoIndeed they do say that. My – admittedly rather poor attempt at a – joke was that the ‘command line tool’ to which you were referring is indeed quite usable and user-friendly; as opposed to, say, ed scripts.