On 2015/1/22 17:15, Miroslav Benes wrote:
> On Thu, 22 Jan 2015, Li Bin wrote:
>
>> On 2015/1/21 17:07, Li Bin wrote:
>>> This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
>>>
>>> The method that only allowing the topmost patch on the stack to be
>>> enabled or disabled is
On Thu, 22 Jan 2015, Li Bin wrote:
> On 2015/1/21 17:07, Li Bin wrote:
> > This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
> >
> > The method that only allowing the topmost patch on the stack to be
> > enabled or disabled is unreasonable. Such as the following case:
> >
> > -
On Thu, 22 Jan 2015, Li Bin wrote:
On 2015/1/21 17:07, Li Bin wrote:
This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
The method that only allowing the topmost patch on the stack to be
enabled or disabled is unreasonable. Such as the following case:
- do live
On 2015/1/22 17:15, Miroslav Benes wrote:
On Thu, 22 Jan 2015, Li Bin wrote:
On 2015/1/21 17:07, Li Bin wrote:
This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
The method that only allowing the topmost patch on the stack to be
enabled or disabled is unreasonable. Such as the
On 2015/1/21 17:07, Li Bin wrote:
> This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
>
> The method that only allowing the topmost patch on the stack to be
> enabled or disabled is unreasonable. Such as the following case:
>
> - do live patch1
> - disable patch1
>
On 2015/1/21 22:36, Seth Jennings wrote:
> On Wed, Jan 21, 2015 at 03:06:38PM +0100, Jiri Kosina wrote:
>> On Wed, 21 Jan 2015, Li Bin wrote:
>>
>>> This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
>>>
>>> The method that only allowing the topmost patch on the stack to be
>>> enabled
On Wed, Jan 21, 2015 at 03:06:38PM +0100, Jiri Kosina wrote:
> On Wed, 21 Jan 2015, Li Bin wrote:
>
> > This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
> >
> > The method that only allowing the topmost patch on the stack to be
> > enabled or disabled is unreasonable. Such as the
On Wed, 21 Jan 2015, Li Bin wrote:
> This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
>
> The method that only allowing the topmost patch on the stack to be
> enabled or disabled is unreasonable. Such as the following case:
>
> - do live patch1
> - disable patch1
>
This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
The method that only allowing the topmost patch on the stack to be
enabled or disabled is unreasonable. Such as the following case:
- do live patch1
- disable patch1
- do live patch2 //error
Now, we will never
On 2015/1/21 17:07, Li Bin wrote:
This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
The method that only allowing the topmost patch on the stack to be
enabled or disabled is unreasonable. Such as the following case:
- do live patch1
- disable patch1
- do
On 2015/1/21 22:36, Seth Jennings wrote:
On Wed, Jan 21, 2015 at 03:06:38PM +0100, Jiri Kosina wrote:
On Wed, 21 Jan 2015, Li Bin wrote:
This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
The method that only allowing the topmost patch on the stack to be
enabled or disabled is
This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
The method that only allowing the topmost patch on the stack to be
enabled or disabled is unreasonable. Such as the following case:
- do live patch1
- disable patch1
- do live patch2 //error
Now, we will never
On Wed, Jan 21, 2015 at 03:06:38PM +0100, Jiri Kosina wrote:
On Wed, 21 Jan 2015, Li Bin wrote:
This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
The method that only allowing the topmost patch on the stack to be
enabled or disabled is unreasonable. Such as the following
On Wed, 21 Jan 2015, Li Bin wrote:
This reverts commit 83a90bb1345767f0cb96d242fd8b9db44b2b0e17.
The method that only allowing the topmost patch on the stack to be
enabled or disabled is unreasonable. Such as the following case:
- do live patch1
- disable patch1
- do
14 matches
Mail list logo