On Fri, Jun 14, 2013 at 12:10 PM, Owen Williams wrote:
> On Fri, 2013-06-14 at 10:55 -0400, RJ Ryan wrote:
> > Nice -- those instructions worked for me to recover an existing branch
> > (like http://github.com/xrg/mixxx branch xrg-1.10) except:
> >
> >
> > 1) bzr export failed -- does that synta
On Fri, 2013-06-14 at 10:55 -0400, RJ Ryan wrote:
> Nice -- those instructions worked for me to recover an existing branch
> (like http://github.com/xrg/mixxx branch xrg-1.10) except:
>
>
> 1) bzr export failed -- does that syntax work? Maybe curl/wget
> git-filter-branch-command-all.sh from baz
Nice -- those instructions worked for me to recover an existing branch
(like http://github.com/xrg/mixxx branch xrg-1.10) except:
1) bzr export failed -- does that syntax work? Maybe curl/wget
git-filter-branch-command-all.sh from bazaar.launchpad.net instead?
2) Don't see the purpose of branchn
Hi Owen,
I agree to Nathan, that we should at least describe an "offical" way how to
Do this.
something like this: (draft; untested)
1. rename your original repository to mixxx-legacy
2. fork mixxxdj/mixxx on Github
3. git clone git://github.com//mixxx.git
4. git remote add upstream git://github
I'll reach out to the owners and ask them to take them down. Not much else
to do there I think...
On Thu, Jun 13, 2013 at 2:09 AM, Daniel Schürmann wrote:
> Hi Owen,
>
> Are previously mad git clones in track of our new repository? Or is there
> a way to manage it with your scripts?
>
> https://
Hi Owen,
Are previously mad git clones in track of our new repository? Or is there a
way to manage it with your scripts?
https://github.com/search?q=mixxx&ref=cmdform
gives 27 results.
Most eye catching:
xrg/mixxx "Unofficial mirror of lp:mixxx DJ software"
This one is also on top of Google sea
