From: Jan Kiszka <jan.kiszka@domain.hid>
To: Philippe Gerum <rpm@xenomai.org>
Cc: xenomai@xenomai.org, Oliver Schlenker <oliver.schlenker@domain.hid>
Subject: Re: [Xenomai-core] [PATCH 0/2] fork-safe rt_print, rt_syslog extension
Date: Mon, 26 Oct 2009 09:14:05 +0100 [thread overview]
Message-ID: <4AE55A4D.6010106@domain.hid> (raw)
In-Reply-To: <1256402324.2862.495.camel@domain.hid>
[-- Attachment #1: Type: text/plain, Size: 1013 bytes --]
Philippe Gerum wrote:
> On Sat, 2009-10-24 at 10:03 +0200, Jan Kiszka wrote:
>> Please pull Oliver's rt_print patches from
>>
>> git://xenomai.org/xenomai-jki.git for-upstream
>>
>>
>> Oliver Schlenker (2):
>> Fork-safe rt_print
>> Syslog extension of rt_print
>>
>> include/rtdk.h | 2 +
>> src/rtdk/rt_print.c | 72 ++++++++++++++++++++++++++++++++++++++++++++++-----
>> 2 files changed, 67 insertions(+), 7 deletions(-)
>>
>> PS: Trying to manage patches by hand is doomed to fail. I can only
>> recommend anyone investing the time to get familiar with basic git
>> commands. It quickly pays off, even for managing only private changes.
>
> Please, make sure to provide a prefix in your short log; this makes
> sorting the short logs for changes by topic a bit easier. E.g.
>
> rtdk: fork-safe rt_print
> rtdk: syslog extension of rt_print
>
As you already merged it - too late to fix. Sorry, will try to avoid
forgetting this in the future.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 257 bytes --]
prev parent reply other threads:[~2009-10-26 8:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-24 8:03 [Xenomai-core] [PATCH 0/2] fork-safe rt_print, rt_syslog extension Jan Kiszka
2009-10-24 8:03 ` [Xenomai-core] [PATCH 1/2] Fork-safe rt_print Jan Kiszka
2009-10-24 8:03 ` [Xenomai-core] [PATCH 2/2] Syslog extension of rt_print Jan Kiszka
2009-10-24 16:38 ` [Xenomai-core] [PATCH 0/2] fork-safe rt_print, rt_syslog extension Philippe Gerum
2009-10-26 8:14 ` Jan Kiszka [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AE55A4D.6010106@domain.hid \
--to=jan.kiszka@domain.hid \
--cc=oliver.schlenker@domain.hid \
--cc=rpm@xenomai.org \
--cc=xenomai@xenomai.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.