On 14/11/2012 18:06, Daniel Silverstone wrote:
> On Wed, Nov 14, 2012 at 05:25:03PM +0100, François Revol wrote:
>> I was wondering which was the best way to get back an old branch from
>> svn into a usable git branch... (namely the gopher one)
>
> If the branches were ported across then they're available in a hidden repo
> which I can restore from. However I think as discussed on IRC, we'd not be
> interested in the gopher support being in the main netsurf repository, even on
> a branch.
Well, in any case, that wasn't the question, it could live locally or on
github for now anyway, the question was how to do it :p
I supposed there was a repos used for the conversion but I didn't know
if it had those as well.
Still I'm quite sure there might be some interest from people on the
ancients platforms we are among the few to still support. I recall
reading forums posts asking for gopher clients on Atari or Amiga even
last year. And it's not like it requires patching every file. The few
touched files (namely just the curl fetcher IIRC) could probably be
hooked in a cleaner way over time I suppose.
>> I was thinking either:
>> - make patches manually from svn and apply this to a git checkout from
>> the base rev, then rebase and push to the public repos,
>
> That might be easiest for you.
Yeah I ended up using grep sed and other friends to generate the diffs.
Still, if you could send me off-list properly formatted git patches from
branches/mmu_man/netsurf-gopher-support-v3 since r13790
878212a0de6fdbcaa37a1635491b37224779b34c that'd be even cleaner.
>> - or create a repos using git-svn, add it as a remote, cherry pick the
>> commits into a branch from the base commit from master, rebase it, and
>> push it public.
>
> You could do that, but I'll warn you that git-svn is really slow and grungy.
Hence my request for advice.
Thanks for the first useful answer for the day :-p
François.
No comments:
Post a Comment