[Mixxx-devel] Legacy git Mixxx repositories

2013-06-12 Thread Daniel Schürmann
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

Re: [Mixxx-devel] Git / GitHub migration nearing completion

2013-06-12 Thread Daniel Schürmann
Hi RJ >> If I understand it right, git has user credentials per repository while bzr has it per branch, we should deal with it. > Credentials aren't built into git -- if you have write access to the repo then you can write to it. So GitHub is in charge > of credentials here. You can configure oth

Re: [Mixxx-devel] Git / GitHub migration nearing completion

2013-06-12 Thread RJ Ryan
On Wed, Jun 12, 2013 at 6:45 PM, Daniel Schürmann wrote: > Hi RJ, > > Fine news! > > Mixxx has 122 active Launchpad branches. Does it really make sense to > convert all of them to git? In which condition is the Owens converter? Is > it possible to provide it, so that we can convert branches when r

Re: [Mixxx-devel] Git / GitHub migration nearing completion

2013-06-12 Thread Owen Williams
I actually committed the migration scripts to trunk in the scripts/ folder just in case of emergency. There's lots of references to /home/owen in them -- I left those unedited on purpose. I didn't want to put the scripts there and have people think they could just run the scripts blind. But feel

Re: [Mixxx-devel] bug reporting in GitHub

2013-06-12 Thread RJ Ryan
Sorry, should have mentioned. Bug tracking and project management will still happen on Launchpad. GitHub is only for code hosting. On Wed, Jun 12, 2013 at 6:45 PM, wrote: > Guys, how do you report teh bugs? I seen no way of any kind. > > ~RAWRR > > > > --

Re: [Mixxx-devel] Git / GitHub migration nearing completion

2013-06-12 Thread Daniel Schürmann
Hi RJ, Fine news! Mixxx has 122 active Launchpad branches. Does it really make sense to convert all of them to git? In which condition is the Owens converter? Is it possible to provide it, so that we can convert branches when required by ourselves? The normal git workflow is to clone the reposit

[Mixxx-devel] bug reporting in GitHub

2013-06-12 Thread re-cycle
Guys, how do you report teh bugs? I seen no way of any kind. ~RAWRR -- This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev ___

Re: [Mixxx-devel] Git / GitHub migration nearing completion

2013-06-12 Thread Philip Whelan
Thank you all very much! This is great! Hopefully I'll get a branch or two up soon. I've seen the recent discussions and it looks like the merges do create more feedback. Cheers and congratulations! On Wed, Jun 12, 2013 at 2:51 PM, RJ Ryan wrote: > Hi all, > > Just wanted to give a status upda

[Mixxx-devel] Git / GitHub migration nearing completion

2013-06-12 Thread RJ Ryan
Hi all, Just wanted to give a status update on the Git migration. We're almost done! https://github.com/mixxxdj/mixxx *tl:dr -- stop committing to Launchpad. Make a GitHub account and fork the Mixxx repo. Push changes and personal branches to your forks and make pull requests to get them merged

Re: [Mixxx-devel] need help with Baazar merging advanced_autodj

2013-06-12 Thread Daniel Schürmann
final my problem is solved. First, I did a a revers merge of the faulty commits, which results in a mixxx.moved folder. bzr merge -r3191..3190 The mixxx.moved folder was reintegrate in the original mixxx folder by bzr move mixxx.moved mixxx Luckily the revision history of the content of the mixxx