Re: Wrong -dirty suffix set by setlocalversion (was: BUG in git diff-index)

How about something like this? It ignores attributes that should have no bearing on whether the kernel is considered dirty. Copied trees with no other changes would no longer be marked with -dirty. Plus it works on read-only media since no index updating is required. Would this also be considered

Re: [RFC 4/7] LTTng instrumentation kernel

x27; intent. I assume LTTng uses it for some purpose, but it's not required to use the markers added by the patch. Also, if list_modules() remains, the 0 should be removed from "__trace_mark(0, ..." Mike Mason - To unsubscribe from this list: send the line "unsubscribe linu

Re: [RFC 4/7] LTTng instrumentation kernel

This patch uses _trace_mark in lockdep.c and printk.c. I assume they should be trace_mark (no '_' prefix). Mike Mason Mathieu Desnoyers wrote: Core kernel events. *not* present in this patch because they are architecture specific : - syscall entry/exit - traps - kernel threa

Re: [to-be-posted-soon] Multiple handlers per marker

Mathieu Desnoyers wrote: * Mike Mason ([EMAIL PROTECTED]) wrote: Mathieu Desnoyers wrote: * Mathieu Desnoyers ([EMAIL PROTECTED]) wrote: * Mathieu Desnoyers ([EMAIL PROTECTED]) wrote: * Mike Mason ([EMAIL PROTECTED]) wrote: Hi Mathieu, Are you aware of any working being done to allow

Re: [to-be-posted-soon] Multiple handlers per marker

Mathieu Desnoyers wrote: * Mathieu Desnoyers ([EMAIL PROTECTED]) wrote: * Mathieu Desnoyers ([EMAIL PROTECTED]) wrote: * Mike Mason ([EMAIL PROTECTED]) wrote: Hi Mathieu, Are you aware of any working being done to allow multiple handlers to be attached to a marker? Something like what