On 5/2/20 5:17 pm, Sebastian Huber wrote:
> On 05/02/2020 07:20, Chris Johns wrote:
>
>> On 5/2/20 5:12 pm, Sebastian Huber wrote:
>>> On 05/02/2020 00:18, Chris Johns wrote:
Does this mean any RSB reference in it's history breaks with the new repo?
>>> Yes, in the new GCC repository is a com
On 05/02/2020 07:20, Chris Johns wrote:
On 5/2/20 5:12 pm, Sebastian Huber wrote:
On 05/02/2020 00:18, Chris Johns wrote:
Does this mean any RSB reference in it's history breaks with the new repo?
Yes, in the new GCC repository is a completely new history.
Does this mean we can directly ref
On 5/2/20 5:12 pm, Sebastian Huber wrote:
> On 05/02/2020 00:18, Chris Johns wrote:
>>
>> Does this mean any RSB reference in it's history breaks with the new repo?
>
> Yes, in the new GCC repository is a completely new history.
>
Does this mean we can directly reference the new repo and the mir
On 05/02/2020 00:18, Chris Johns wrote:
On 5/2/20 12:13 am, Sebastian Huber wrote:
Hello,
it seems GCC finished the Git conversion:
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=summary
This means our GCC Git mirror refers to a deprecated Git repository.
Is this the mirror on github?
GCC
On 5/2/20 12:13 am, Sebastian Huber wrote:
> Hello,
>
> it seems GCC finished the Git conversion:
>
> https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=summary
>
> This means our GCC Git mirror refers to a deprecated Git repository.
Is this the mirror on github?
Does this mean any RSB reference i
Hello,
it seems GCC finished the Git conversion:
https://gcc.gnu.org/git/gitweb.cgi?p=gcc.git;a=summary
This means our GCC Git mirror refers to a deprecated Git repository.
___
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinf
