For things that are currently considered needed for Nemo MW, just send a
mail here or msg me and we'll get it set up.

We're lagging a tiny bit behind in the exact repos, so if they are part of
mer core, they're part..

2015-07-29 11:17 GMT+02:00 David Greaves <[email protected]>:

> On 29/07/15 09:43, Denis Zalewsky wrote:
>
>> Hi,
>>
>> On Tue, Jul 28, 2015 at 5:22 PM, David Greaves <[email protected]>
>> wrote:
>>
>>> Creating git repos
>>>
>>> We've replicated about 170 repos from github projects:
>>>   https://github.com/[nemomobile, nemomobile-packages, mer-packages]
>>>
>>> What I've done (hopefully!) is to take the current/old Mer master branch
>>> and
>>> rename it to master-premerge. Then I've set mer/master to be the github
>>> master.
>>>
>>> In some cases where we've moved on from the old 'tarballs in git' there
>>> may
>>> be no commits in common and we'll end up with an 'orphan' branch (google
>>> it)
>>>
>>> Maintainers should check the repos to make sure I've not messed up :)
>>>
>>
>> Could you also describe how to add missing projects (e.g. not yet
>> cloned from github)?
>>
>
> So in general Carsten (guided by maintainers) will decide which 'new'
> projects go in mer-core and once he gives the nod I'll add it repos on
> g.m.o, packages on OBS and webhooks. Ideally we'll manage this through a
> bug.
>
> If there's just an admin thing (ie I missed a migration and the source for
> an existing package isn't on g.m.o) then I'll take care of it. Either log a
> bug or just ask me on the ml/irc.
>
> David
>
> --
> "Don't worry, you'll be fine; I saw it work in a cartoon once..."
>
>
> --
> To unsubscribe send a mail to : <mailto:
> [email protected]>
>
>

Reply via email to