duplicate repositories mynewt_arduino_zero, mynewt_nordic, mynewt_stm32f3

[marko kiiskila <ma...@runtime.io>]

Hi,

currently we have these repositories (with almost the same contents),
the new one in github.com/runtimeco <http://github.com/runtimeco> and old one in github.com/runtimeinc <http://github.com/runtimeinc>

Although from pulling point of view it is somewhat more convenient to users to
have them like this (as the old versions of documentation were point to runtimeinc,
new versions point to runtimeco), it is painful to maintain. We’ve already made mistakes
when tagging; pull requests were made against old repo etc.

Would anyone object if I remove the old repositories completely? It appears that
you can do git remote set-url to point to new repo, if people have lingering links.

Re: duplicate repositories mynewt_arduino_zero, mynewt_nordic, mynewt_stm32f3

[marko kiiskila <ma...@runtime.io>]

> On Jul 11, 2017, at 2:53 PM, marko kiiskila <ma...@runtime.io> wrote:
> 
> 
>> On Jul 11, 2017, at 11:09 AM, Fabio Utzig <ut...@utzig.org> wrote:
>> 
>> On Tue, Jul 11, 2017, at 12:51 PM, Todd Mitton wrote:
>>> It would be nice to transfer the ownership of the repos from the
>>> runtimeinc
>>> organization to the runtimeco organization. That way github would
>>> redirect
>>> from the old location to the new location and old links would continue to
>>> work. You'd have to delete the repos from runtimeco, then transfer from
>>> runtimeinc to runtimeco.
>> 
>> Apart from redirection it also transfers stars/forks.
> 
> Fair enough. I’ll apply changes made to runtimeco version to runtimeinc version,
> remove runtimeco version, and transfer the ownership from runtimeinc to runtimeco.

Ok, done.

Re: duplicate repositories mynewt_arduino_zero, mynewt_nordic, mynewt_stm32f3

[marko kiiskila <ma...@runtime.io>]

> On Jul 11, 2017, at 11:09 AM, Fabio Utzig <ut...@utzig.org> wrote:
> 
> On Tue, Jul 11, 2017, at 12:51 PM, Todd Mitton wrote:
>> It would be nice to transfer the ownership of the repos from the
>> runtimeinc
>> organization to the runtimeco organization. That way github would
>> redirect
>> from the old location to the new location and old links would continue to
>> work. You'd have to delete the repos from runtimeco, then transfer from
>> runtimeinc to runtimeco.
> 
> Apart from redirection it also transfers stars/forks.

Fair enough. I’ll apply changes made to runtimeco version to runtimeinc version,
remove runtimeco version, and transfer the ownership from runtimeinc to runtimeco.
—
M

Re: duplicate repositories mynewt_arduino_zero, mynewt_nordic, mynewt_stm32f3

[Fabio Utzig <ut...@utzig.org>]

On Tue, Jul 11, 2017, at 12:51 PM, Todd Mitton wrote:
> It would be nice to transfer the ownership of the repos from the
> runtimeinc
> organization to the runtimeco organization. That way github would
> redirect
> from the old location to the new location and old links would continue to
> work. You'd have to delete the repos from runtimeco, then transfer from
> runtimeinc to runtimeco.

Apart from redirection it also transfers stars/forks.

Re: duplicate repositories mynewt_arduino_zero, mynewt_nordic, mynewt_stm32f3

[Todd Mitton <mi...@runtime.io>]

It would be nice to transfer the ownership of the repos from the runtimeinc
organization to the runtimeco organization. That way github would redirect
from the old location to the new location and old links would continue to
work. You'd have to delete the repos from runtimeco, then transfer from
runtimeinc to runtimeco.

-Todd

On Tue, Jul 11, 2017 at 11:03 AM, Szymon Janc <sz...@codecoup.pl>
wrote:

> Hi Marko,
>
> On 11 July 2017 at 01:16, marko kiiskila <ma...@runtime.io> wrote:
> >
> > Hi,
> >
> > currently we have these repositories (with almost the same contents),
> > the new one in github.com/runtimeco <http://github.com/runtimeco> and
> old one in github.com/runtimeinc <http://github.com/runtimeinc>
> >
> > Although from pulling point of view it is somewhat more convenient to
> users to
> > have them like this (as the old versions of documentation were point to
> runtimeinc,
> > new versions point to runtimeco), it is painful to maintain. We’ve
> already made mistakes
> > when tagging; pull requests were made against old repo etc.
> >
> > Would anyone object if I remove the old repositories completely? It
> appears that
> > you can do git remote set-url to point to new repo, if people have
> lingering links.
>
> I'm for removing old repos. In worst case people will ask here what is
> going on.
> This is less evil than let them use old unmaintained code :)
>
> --
> pozdrawiam
> Szymon K. Janc
>

Re: duplicate repositories mynewt_arduino_zero, mynewt_nordic, mynewt_stm32f3

[Szymon Janc <sz...@codecoup.pl>]

Hi Marko,

On 11 July 2017 at 01:16, marko kiiskila <ma...@runtime.io> wrote:
>
> Hi,
>
> currently we have these repositories (with almost the same contents),
> the new one in github.com/runtimeco <http://github.com/runtimeco> and old one in github.com/runtimeinc <http://github.com/runtimeinc>
>
> Although from pulling point of view it is somewhat more convenient to users to
> have them like this (as the old versions of documentation were point to runtimeinc,
> new versions point to runtimeco), it is painful to maintain. We’ve already made mistakes
> when tagging; pull requests were made against old repo etc.
>
> Would anyone object if I remove the old repositories completely? It appears that
> you can do git remote set-url to point to new repo, if people have lingering links.

I'm for removing old repos. In worst case people will ask here what is going on.
This is less evil than let them use old unmaintained code :)

-- 
pozdrawiam
Szymon K. Janc