On Fri, Jun 22, 2018 at 06:24:54AM +0800, Douglas Goldstein wrote:
> > >>> Working patch by patch isn't feasible because of the renames.
> > >>
> > >> I don't understand - how does path/file naming conflict with working
> > >> patch by patch? Surely a relatively simple sed command could be used
>
> On Jun 25, 2018, at 11:13 AM, George Dunlap wrote:
>
>
>
>> On Jun 22, 2018, at 4:11 PM, Julien Grall wrote:
>>
>> Hi,
>>
>> On 06/22/2018 08:42 AM, Jan Beulich wrote:
>> On 22.06.18 at 00:24, wrote:
Working patch by patch isn't feasible because of the renames.
>>>
>>>
> On Jun 22, 2018, at 4:11 PM, Julien Grall wrote:
>
> Hi,
>
> On 06/22/2018 08:42 AM, Jan Beulich wrote:
> On 22.06.18 at 00:24, wrote:
>>> Working patch by patch isn't feasible because of the renames.
>>
>> I don't understand - how does path/file naming conflict with workin
>>> On 22.06.18 at 10:11, wrote:
> On 06/22/2018 08:42 AM, Jan Beulich wrote:
> On 22.06.18 at 00:24, wrote:
>>> Working patch by patch isn't feasible because of the renames.
>>
>> I don't understand - how does path/file naming conflict with working
>> patch by patch? Surely a
Hi,
On 06/22/2018 08:42 AM, Jan Beulich wrote:
On 22.06.18 at 00:24, wrote:
Working patch by patch isn't feasible because of the renames.
I don't understand - how does path/file naming conflict with working
patch by patch? Surely a relatively simple sed command could be used
to change the pa
>>> On 22.06.18 at 00:24, wrote:
>> >>> Working patch by patch isn't feasible because of the renames.
>> >>
>> >> I don't understand - how does path/file naming conflict with working
>> >> patch by patch? Surely a relatively simple sed command could be used
>> >> to change the paths in each patch
> >>> Working patch by patch isn't feasible because of the renames.
> >>
> >> I don't understand - how does path/file naming conflict with working
> >> patch by patch? Surely a relatively simple sed command could be used
> >> to change the paths in each patch according to our tree layout. That's
>
>>> On 21.06.18 at 10:44, wrote:
>
>> On Jun 21, 2018, at 4:37 PM, Jan Beulich wrote:
>>
> On 21.06.18 at 10:28, wrote:
>>> On 21/06/18 16:13, Jan Beulich wrote:
>>> On 21.06.18 at 04:10, wrote:
> From: Doug Goldstein
>
> From: Doug Goldstein
>
> Import the fo
> On Jun 21, 2018, at 4:37 PM, Jan Beulich wrote:
>
On 21.06.18 at 10:28, wrote:
>> On 21/06/18 16:13, Jan Beulich wrote:
>> On 21.06.18 at 04:10, wrote:
From: Doug Goldstein
From: Doug Goldstein
Import the following files and directories from the Linux v
>>> On 21.06.18 at 10:28, wrote:
> On 21/06/18 16:13, Jan Beulich wrote:
> On 21.06.18 at 04:10, wrote:
>>> From: Doug Goldstein
>>>
>>> From: Doug Goldstein
>>>
>>> Import the following files and directories from the Linux v4.17 tag
>>> (commit id 29dcea88779c856c7dc92040a0c01233263101d4):
On 21/06/18 16:13, Jan Beulich wrote:
On 21.06.18 at 04:10, wrote:
>> From: Doug Goldstein
>>
>> From: Doug Goldstein
>>
>> Import the following files and directories from the Linux v4.17 tag
>> (commit id 29dcea88779c856c7dc92040a0c01233263101d4):
>> - scripts/kconfig/ -> xen/tools/kconfig
>>> On 21.06.18 at 04:10, wrote:
> From: Doug Goldstein
>
> From: Doug Goldstein
>
> Import the following files and directories from the Linux v4.17 tag
> (commit id 29dcea88779c856c7dc92040a0c01233263101d4):
> - scripts/kconfig/ -> xen/tools/kconfig/
> - scripts/Makefile.host -> xen/tools/kco
On Thu, Jun 21, 2018 at 10:10:52AM +0800, dougt...@icloud.com wrote:
> From: Doug Goldstein
>
> From: Doug Goldstein
>
> Import the following files and directories from the Linux v4.17 tag
> (commit id 29dcea88779c856c7dc92040a0c01233263101d4):
> - scripts/kconfig/ -> xen/tools/kconfig/
> - scr
On 21/06/18 10:10, dougt...@icloud.com wrote:
> From: Doug Goldstein
>
> Import the following files and directories from the Linux v4.17 tag
> (commit id 29dcea88779c856c7dc92040a0c01233263101d4):
> - scripts/kconfig/ -> xen/tools/kconfig/
> - scripts/Makefile.host -> xen/tools/kconfig/Makefile.ho
14 matches
Mail list logo
