From: Pavel Vasilyev <pavel@pavlinux.ru>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
linux-rt-users <linux-rt-users@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
rostedt@goodmis.org, John Kacur <jkacur@redhat.com>
Subject: Re: [ANNOUNCE] 3.12.12-rt19
Date: Mon, 24 Feb 2014 02:55:20 +0400 [thread overview]
Message-ID: <530A7C58.2060009@pavlinux.ru> (raw)
In-Reply-To: <alpine.DEB.2.02.1402232211300.21251@ionos.tec.linutronix.de>
[-- Attachment #1: Type: text/plain, Size: 809 bytes --]
24.02.2014 01:13, Thomas Gleixner пишет:
> On Sun, 23 Feb 2014, Pavel Vasilyev wrote:
>> 23.02.2014 23:13, Pavel Vasilyev пишет:
>>
>>> But not -rt1, -rt2, -rt3 -rt4, .... -rt99
>>
>> Or
>>
>> 3.12-rt1,
>> 3.12-rt2,
>> ...
>> 3.12-rt33,
>> ...
>> 3.12-rt111,
>> ...
>> 3.12-rt999
>> ...
>>
>> Now, to have to roll back all my changes, then work -rt patch,
>> then impose SUBLEVEL mainline diff, then last -rt patch, then my сhanges.
>
> So we need a different numbering scheme just because your workflow is
> completely backwards?
No, because in positional number systems, an increase in the senior level,
junior reset, but not stays the same. Mainline kernel and patches is senior level.
--
Pavel.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-02-23 22:56 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-23 18:47 [ANNOUNCE] 3.12.12-rt19 Sebastian Andrzej Siewior
2014-02-23 19:13 ` Pavel Vasilyev
2014-02-23 19:29 ` Pavel Vasilyev
2014-02-23 21:13 ` Thomas Gleixner
2014-02-23 22:55 ` Pavel Vasilyev [this message]
2014-02-27 3:07 ` Steven Rostedt
2014-03-02 1:48 ` Fernando Lopez-Lezcano
2014-03-07 11:18 ` nouveau crash due to missing channel (WAS: Re: [ANNOUNCE] 3.12.12-rt19) Sebastian Andrzej Siewior
2014-03-07 11:36 ` Maarten Lankhorst
2014-03-07 11:36 ` Maarten Lankhorst
2014-03-07 11:53 ` Sebastian Andrzej Siewior
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=530A7C58.2060009@pavlinux.ru \
--to=pavel@pavlinux.ru \
--cc=bigeasy@linutronix.de \
--cc=jkacur@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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.