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 branchname-update vs. branchname. I just used
'branchname'.
3) "git branch -u" is only in git 1.8 and onwards "git push -u origin
branchname" is equivalent and works in 1.7 so the git branch -u command can
be dropped.
4) I would also add details at the end of the instructions to remove the
legacy remote and delete data that was imported from 'legacy' when you ran
git fetch legacy.
My personal fork before recovering xrg-1.0 is 322MB, my personal fork after
recovering just xrg-1.10 (which is only 3 small commits): 486MB.
$ git remote rm legacy
$ git gc --aggressive
Afterwards it's 196MB (we should probably do this to mixxxdj/mixxx as
well).
On Fri, Jun 14, 2013 at 1:53 AM, Daniel Schürmann <dasch...@mixxx.org>wrote:
> 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/<user>/mixxx.git
> 4. git remote add upstream git://github.com/mixxdj/mixxx.git
> 5. git remote add legacy git://github.com/<user>/mixxx-legacy.git
> 5. git fetch legacy
> 6. git checkout -b branchname-update remotes/legacy/branchname
> 7. git checkout -b branchname
> 8. pick a unique branchname if already exists!
> 9. bzr export ../lp_to_github lp:mixxx/mixxx/scripts/lp_to_github
> 10. ../lp_to_github/git-filter-branch-command-all.sh
> 11. git branch -u origin branchname
> 12. git push origin branchname
> 13. repeat from 6. for all branches
>
> please correct if can be improved!
> Where is the right place to publish this?
>
> Kind regards,
>
> Daniel
>
>
>
>
> 2013/6/13 nathan dotz <nathan.d...@gmail.com>
>
>> Better yet, ask them to turn theirs into forks of the official one :)
>>
>>
>> Also, I haven't had time to contribute much noise to this recently, but
>> good work on the github migration everyone! I think this is a great step in
>> the right direction!
>>
>> On June 13, 2013 at 3:14:40 PM, RJ Ryan (rr...@mixxx.org) wrote:
>>
>> 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 <dasch...@mixxx.org>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://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 search results when you search
>>> "Github Mixxx" Our offical repository is on 8 :-(
>>>
>>>
>>> Kind regards,
>>>
>>> Daniel
>>>
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> This SF.net email is sponsored by Windows:
>>>
>>> Build for Windows Store.
>>>
>>> http://p.sf.net/sfu/windows-dev2dev
>>> _______________________________________________
>>> Get Mixxx, the #1 Free MP3 DJ Mixing software Today
>>> http://mixxx.org
>>>
>>>
>>> Mixxx-devel mailing list
>>> Mixxx-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/mixxx-devel
>>>
>>
>> --
>> @nathandotz
>> github.com/sleepynate | www.sleepynate.com
>>
>
>
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:
Build for Windows Store.
http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Get Mixxx, the #1 Free MP3 DJ Mixing software Today
http://mixxx.org
Mixxx-devel mailing list
Mixxx-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mixxx-devel
