[genivi-dlt] [Patch] Several patchs for Bugfix and improvements

Jeremiah Foster jeremiah.foster at pelagicore.com
Tue Oct 11 09:48:43 EDT 2016


On Tue, Oct 11, 2016 at 7:14 AM, <Alexander.AW.Wenzel at bmw.de> wrote:

> Hello Christoph,
>
> 1) I see no problems with the commit dates. I see the following commits
> from you on github.
> There are always two dates for each commit, one date when the patch is
> created, and another when the patch was applied to the master.
> Perhaps the order of the commits is sometimes changed.
> Which commit do you mean?
>
> Revision: 53cd25f1e37c65d465493df6e7e3ebb0270bd651
> Author: Christoph Lipka <clipka at jp.adit-jv.com>
> Date: 11.05.2016 05:13:58
> Message:
> Add dlt_user_is_logLevel_enabled API
>
> Revision: 5d4ffd73f8d70a7ab04bbae910bb855267d8f510
> Author: Christoph Lipka <clipka at jp.adit-jv.com>
> Date: 18.03.2016 07:49:03
> Message:
> dlt-daemon: Free DltDaemon structure on exit
>
> Revision: 6a8919c637b28fab7cc6f8e87cfca6f13bb8cb1d
> Author: Christoph Lipka <clipka at jp.adit-jv.com>
> Date: 26.01.2016 08:09:21
> Message:
> DLT_PTR: User macro to print pointers
>
> Revision: cc4517dcffc6e5fd66791fca486586ae9b948174
> Author: Christoph Lipka <clipka at jp.adit-jv.com>
> Date: 20.01.2016 06:57:57
> Message:
> MultiNode: Send control messages after connection
>
> Revision: c75c984cfb1c6d154b14ebfca64c8222c4013c6b
> Author: Christoph Lipka <clipka at jp.adit-jv.com>
> Date: 18.01.2016 02:28:46
> Message:
> MultiNode: Send serialheader if specified in dlt.conf
>
> Revision: bc09757d465d4ee5728157dce4fed0f71841daa7
> Author: Christoph Lipka <clipka at jp.adit-jv.com>
> Date: 16.03.2016 08:05:53
> Message:
> Offline logstorage: On Demand triggering for syncing Logstorage cache and
> support long options
>
> Revision: 71ab66bb38783b6470844313d80b6dde6e514894
> Author: Christoph Lipka <clipka at jp.adit-jv.com>
> Date: 11.12.2015 03:40:11
> Message:
> Offline logstorage: Fix invalid filter configuration handling
>
> 2) The old repository from GENIVI is no longer updated. I even do not have
> any write access anymore. We have to ask @Jeremiah, if any hint can be
> displayed on the old repositories, that it is outdated.
>

​We're actually working on those repos now. @Christoph -- you want all the
changes in the DLT daemon git repo to be pushed to the repos at
git.projects.genivi.org? We can do that but that URL is meant really to be
an archive that people can use to build older versions of GENIVI code.
People working on development or doing new integration should really be
using the updated repos at GitHub. Is there any reason we can't continue to
use GitHub in this case? And if we can't, what info do you want to push to
the archives at git.projects.genivi.org? Should I be focusing on a specific
commit or tag to transfer?

Regards,

Jeremiah​
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.genivi.org/pipermail/genivi-diagnostic-log-and-trace_lists.genivi.org/attachments/20161011/c7f3b4e0/attachment.html>


More information about the genivi-diagnostic-log-and-trace mailing list