Hello, On Tue, Oct 27, 2009 at 07:14:17PM +0100, Thomas Schwinge wrote: > On Tue, Oct 27, 2009 at 07:48:36PM +0200, Sergiu Ivanov wrote: > > A part of the namespace-based translator selection project is the > > filter translator. It is currently here: > > git://github.com/scolobb/filter.git . Is it a good idea to move this > > translator into the incubator.git repository, just like nsmux has > > been? If so, could you please tell me how to do that (so that you > > don't spend your time :-) )? > > This should work, but is untested. :-) Do a checkout of the > incubator. `cd' to that. ``git remote add github--scolobb--filter > git://github.com/scolobb/filter.git'' to add a new remote named > github--scolobb--filter. ``git remote update'' to fetch all > remotes' heads, i.e. the Savannah ones (most probably named > origin/*), and the new github--scolobb--filter/* ones). Then you > can simply do ``git push [SAVANNAH] > github--scolobb--filter/master:filter'' ([SAVANNAH] most likely > being ``origin'') to push what is now locally known as > github--scolobb--filter/master (assuming you want to publish the > master branch) onto Savannah, named filter there. (Or perhaps > filterfs? -- your dice.)
The name should stay ``filter'' because a filter will not publish a virtual filesystem. When I get it working, I'll definitely mention the fact in the documentation :-) > Actually, that push command will likely fail, and instead you'll > have to do the following: ``git push [SAVANNAH] > github--scolobb--filter/master:refs/heads/filter'', i.e. tell the > Savanah server that this shall be a new branch (head) and not a tag, > for example, which that remote server can't't know yet. Yep, I had to use the second version. Thank you very much for your detailed explanation which leaves no room for ambiguity :-) I've just added the filter to the incubator :-) Regards, scolobb
