Am 14.06.2018 um 09:43 schrieb Sebastian Huber:
> On 14/06/18 09:40, Chris Johns wrote:
>> On 14/6/18 5:34 pm, Christian Mauderer wrote:
>>> Am 14.06.2018 um 09:31 schrieb Chris Johns:
On 14/6/18 4:27 pm, Sebastian Huber wrote:
> Hello,
>
> On 13/06/18 13:27, Christian Mauderer wro
On 14/06/18 09:40, Chris Johns wrote:
On 14/6/18 5:34 pm, Christian Mauderer wrote:
Am 14.06.2018 um 09:31 schrieb Chris Johns:
On 14/6/18 4:27 pm, Sebastian Huber wrote:
Hello,
On 13/06/18 13:27, Christian Mauderer wrote:
OK. I'll have a look at all repos in the next few days where the
subm
On 14/6/18 5:34 pm, Christian Mauderer wrote:
> Am 14.06.2018 um 09:31 schrieb Chris Johns:
>> On 14/6/18 4:27 pm, Sebastian Huber wrote:
>>> Hello,
>>>
>>> On 13/06/18 13:27, Christian Mauderer wrote:
OK. I'll have a look at all repos in the next few days where the
submodule is used and
On 14/06/18 09:31, Chris Johns wrote:
On 14/6/18 4:27 pm, Sebastian Huber wrote:
Hello,
On 13/06/18 13:27, Christian Mauderer wrote:
OK. I'll have a look at all repos in the next few days where the
submodule is used and change the URL. I'll post a message to the mailing
lists as soon as it is
Am 14.06.2018 um 09:31 schrieb Chris Johns:
> On 14/6/18 4:27 pm, Sebastian Huber wrote:
>> Hello,
>>
>> On 13/06/18 13:27, Christian Mauderer wrote:
>>> OK. I'll have a look at all repos in the next few days where the
>>> submodule is used and change the URL. I'll post a message to the mailing
>>>
On 14/6/18 4:27 pm, Sebastian Huber wrote:
> Hello,
>
> On 13/06/18 13:27, Christian Mauderer wrote:
>> OK. I'll have a look at all repos in the next few days where the
>> submodule is used and change the URL. I'll post a message to the mailing
>> lists as soon as it is done to inform the user tha
Hello,
On 13/06/18 13:27, Christian Mauderer wrote:
OK. I'll have a look at all repos in the next few days where the
submodule is used and change the URL. I'll post a message to the mailing
lists as soon as it is done to inform the user that a "git submodule
sync" fixes the address.
since we h
Am 13.06.2018 um 00:24 schrieb Chris Johns:
> On 12/06/2018 17:45, Christian Mauderer wrote:
>> Am 12.06.2018 um 09:29 schrieb Chris Johns:
>>> On 12/06/2018 17:18, Christian Mauderer wrote:
Am 12.06.2018 um 07:08 schrieb Chris Johns:
> On 09/06/2018 02:45, Christian Mauderer wrote:
>>
On 12/06/2018 17:45, Christian Mauderer wrote:
> Am 12.06.2018 um 09:29 schrieb Chris Johns:
>> On 12/06/2018 17:18, Christian Mauderer wrote:
>>> Am 12.06.2018 um 07:08 schrieb Chris Johns:
On 09/06/2018 02:45, Christian Mauderer wrote:
>
> Did you also note Gedares suggestion to move
Am 12.06.2018 um 09:29 schrieb Chris Johns:
> On 12/06/2018 17:18, Christian Mauderer wrote:
>> Am 12.06.2018 um 07:08 schrieb Chris Johns:
>>> On 09/06/2018 02:45, Christian Mauderer wrote:
Did you also note Gedares suggestion to move the rtems_waf.git to the
public repos? Maybe tha
On 12/06/2018 17:18, Christian Mauderer wrote:
> Am 12.06.2018 um 07:08 schrieb Chris Johns:
>> On 09/06/2018 02:45, Christian Mauderer wrote:
>>>
>>> Did you also note Gedares suggestion to move the rtems_waf.git to the
>>> public repos? Maybe that would be a good idea.
>>>
>>
>> Yes I did and it
Am 12.06.2018 um 09:18 schrieb Christian Mauderer:
> The first one has a longer backward compatibility (relative URLs are
> there since 2007: https://github.com/git/git/commit/f31a522a2d which
> should be somewhere between git 1.5 and git 1.6).
Just noted: That feature has been merged in 1.7.12. S
Am 12.06.2018 um 07:08 schrieb Chris Johns:
> On 09/06/2018 02:45, Christian Mauderer wrote:
>>
>> Did you also note Gedares suggestion to move the rtems_waf.git to the
>> public repos? Maybe that would be a good idea.
>>
>
> Yes I did and it is a good idea. I have move the repo to the top level a
On 09/06/2018 02:45, Christian Mauderer wrote:
>
> Did you also note Gedares suggestion to move the rtems_waf.git to the
> public repos? Maybe that would be a good idea.
>
Yes I did and it is a good idea. I have move the repo to the top level and
updated cgit's config so it is viewable.
Will ne
Am 08.06.2018 um 15:35 schrieb Chris Johns:
>
>
>> On 8 Jun 2018, at 4:21 pm, Christian Mauderer
>> wrote:
>>
>>> Am 06.06.2018 um 09:48 schrieb Christian Mauderer:
>>> In the current version of libbsd, if the --show-commands option is used,
>>> the cwd is passed as a Nod3. Popen does not work
> On 8 Jun 2018, at 4:21 pm, Christian Mauderer
> wrote:
>
>> Am 06.06.2018 um 09:48 schrieb Christian Mauderer:
>> In the current version of libbsd, if the --show-commands option is used,
>> the cwd is passed as a Nod3. Popen does not work with that. Therefore
>> create a string from cwd if
On Fri, Jun 8, 2018 at 2:21 AM, Christian Mauderer
wrote:
> Am 06.06.2018 um 09:48 schrieb Christian Mauderer:
>> In the current version of libbsd, if the --show-commands option is used,
>> the cwd is passed as a Nod3. Popen does not work with that. Therefore
>> create a string from cwd if it isn'
Am 06.06.2018 um 09:48 schrieb Christian Mauderer:
> In the current version of libbsd, if the --show-commands option is used,
> the cwd is passed as a Nod3. Popen does not work with that. Therefore
> create a string from cwd if it isn't already.
> ---
> rtems.py | 2 ++
> 1 file changed, 2 inserti
18 matches
Mail list logo
