Andrew wrote:
> Ho hum. Adding a "why
> this was dropped" to the email seemed too tricky.
I can't speak for all the other clue deprived gits out here, but for
me at least just adding a generic "If this patch was sent on to Linus,
that might be one possible reason it is now dropped from *-mm."
Andrew wrote:
Ho hum. Adding a why
this was dropped to the email seemed too tricky.
I can't speak for all the other clue deprived gits out here, but for
me at least just adding a generic If this patch was sent on to Linus,
that might be one possible reason it is now dropped from *-mm. boiler
Andrew Morton wrote:
Michael Krufky <[EMAIL PROTECTED]> wrote:
However, sometimes there are patches in -mm that are incompatable with
-linus. An example of this is "Pavel's pm_message_t mangling" ...
OK. The way I handle an exceptional case like that is to merge the
Michael Krufky <[EMAIL PROTECTED]> wrote:
>
> Andrew Morton wrote:
>
> >Michael Krufky <[EMAIL PROTECTED]> wrote:
> >
> >
> >>[ tracking mm stuff ]
> >>
> >>
> While we're on the topic of how -mm works, I have a question for you.
> How can I test a kernel source tree (during compilation)
Michael Krufky wrote:
However, sometimes there are patches in -mm that are incompatable with
-linus. An example of this is "Pavel's pm_message_t mangling" ...
Testing for the numbered 2.6.x version isn't enough of a test in a
case like this, but it would be nice to be able to develop against
Andrew Morton wrote:
Michael Krufky <[EMAIL PROTECTED]> wrote:
[ tracking mm stuff ]
While we're on the topic of how -mm works, I have a question for you.
How can I test a kernel source tree (during compilation) to determine
whether it is a -mm tree or a -linus tree?
I will give
Radoslaw "AstralStorm" Szkodzinski <[EMAIL PROTECTED]> wrote:
>
> On Tue, 26 Jul 2005 16:35:21 -0700
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> > I did?
> >
>
> Exactly, I did untar it and I already had a directory called patches.
> Of course cleaning it up took no time, as fortunately
Andrew Morton said:
> Radoslaw "AstralStorm" Szkodzinski <[EMAIL PROTECTED]> wrote:
>>
>> On Tue, 26 Jul 2005 16:11:49 -0700
>> Andrew Morton <[EMAIL PROTECTED]> wrote:
>>
>> >
>> > All done - let me know if it needs anything else.
>> >
>>
>> You got me with a tarball w/o a directory inside. Now
On Tue, 26 Jul 2005 16:35:21 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> I did?
>
Exactly, I did untar it and I already had a directory called patches.
Of course cleaning it up took no time, as fortunately I had no patches with
exactly the same name and no series file in the directory
Radoslaw "AstralStorm" Szkodzinski <[EMAIL PROTECTED]> wrote:
>
> On Tue, 26 Jul 2005 16:11:49 -0700
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> >
> > All done - let me know if it needs anything else.
> >
>
> You got me with a tarball w/o a directory inside. Now I have to clean up the
>
On Tue, 26 Jul 2005 16:11:49 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> All done - let me know if it needs anything else.
>
You got me with a tarball w/o a directory inside. Now I have to clean up the
mess.
Not the first time in life. I think I'll never learn. :)
--
AstralStorm
GPG
Radoslaw "AstralStorm" Szkodzinski <[EMAIL PROTECTED]> wrote:
>
> On Tue, 26 Jul 2005 14:41:49 -0700
> Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> > Michael Krufky <[EMAIL PROTECTED]> wrote:
> > >
> > > [ tracking mm stuff ]
> > >
> >
> > Sigh, sorry. It's hard. -mm is always in flux. I no
On Tue, 26 Jul 2005 15:32:51 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> Andrew Morton <[EMAIL PROTECTED]> wrote:
> >
> > I spose I could emit a broken-out.tar.gz file occasionally (it'd be up to 5
> > times a day),
>
> OK, I did that.
>
Great!
> The kernel.org propagation delay is a
On Tue, 26 Jul 2005 14:41:49 -0700
Andrew Morton <[EMAIL PROTECTED]> wrote:
> Michael Krufky <[EMAIL PROTECTED]> wrote:
> >
> > [ tracking mm stuff ]
> >
>
> Sigh, sorry. It's hard. -mm is always in flux. I no longer send out the
> `patch was dropped' message because it disturbs people.
Andrew Morton <[EMAIL PROTECTED]> wrote:
>
> I spose I could emit a broken-out.tar.gz file occasionally (it'd be up to 5
> times a day), but there's no guarantee that it'll compile, let alone run.
> I could also send a notification to mm-commits when I do so. Would that
> help?
OK, I did that.
Michael Krufky <[EMAIL PROTECTED]> wrote:
>
> [ tracking mm stuff ]
>
Sigh, sorry. It's hard. -mm is always in flux. I no longer send out the
`patch was dropped' message because it disturbs people. The mm-commits
list does not resend a patch when it is changed (other patches folded into
it,
Radoslaw AstralStorm Szkodzinski wrote:
On Tue, 26 Jul 2005 15:45:41 -0400
Michael Krufky <[EMAIL PROTECTED]> wrote:
have filters set up so that my mailer puts all mm-commits messages
from the mailing list into a special "mm-commits" folder. Each time
Andrew releases an -mm kernel, I rename
On Tue, 26 Jul 2005 15:45:41 -0400
Michael Krufky <[EMAIL PROTECTED]> wrote:
> I have filters set up so that my mailer puts all mm-commits messages
> from the mailing list into a special "mm-commits" folder. Each time
> Andrew releases an -mm kernel, I rename my "mm-commits" folder to
>
Radoslaw AstralStorm Szkodzinski wrote:
b) It doesn't say which -mm version are they in.
This is a real PITA, because I have to check patch list one after one to
apply to the newest mm.
I have filters set up so that my mailer puts all mm-commits messages
from the mailing list into a special
I've a question on how to keep in touch with all those patches going into mm
patchset. Yes, I know of and am subscribed to mm-commits list, but it has a
few shortcomings:
a) It doesn't tell which patches went into the mainline.
That's not necessary, as there's always git, but comparing on commit
I've a question on how to keep in touch with all those patches going into mm
patchset. Yes, I know of and am subscribed to mm-commits list, but it has a
few shortcomings:
a) It doesn't tell which patches went into the mainline.
That's not necessary, as there's always git, but comparing on commit
Radoslaw AstralStorm Szkodzinski wrote:
b) It doesn't say which -mm version are they in.
This is a real PITA, because I have to check patch list one after one to
apply to the newest mm.
I have filters set up so that my mailer puts all mm-commits messages
from the mailing list into a special
On Tue, 26 Jul 2005 15:45:41 -0400
Michael Krufky [EMAIL PROTECTED] wrote:
I have filters set up so that my mailer puts all mm-commits messages
from the mailing list into a special mm-commits folder. Each time
Andrew releases an -mm kernel, I rename my mm-commits folder to
Radoslaw AstralStorm Szkodzinski wrote:
On Tue, 26 Jul 2005 15:45:41 -0400
Michael Krufky [EMAIL PROTECTED] wrote:
have filters set up so that my mailer puts all mm-commits messages
from the mailing list into a special mm-commits folder. Each time
Andrew releases an -mm kernel, I rename my
Michael Krufky [EMAIL PROTECTED] wrote:
[ tracking mm stuff ]
Sigh, sorry. It's hard. -mm is always in flux. I no longer send out the
`patch was dropped' message because it disturbs people. The mm-commits
list does not resend a patch when it is changed (other patches folded into
it,
Andrew Morton [EMAIL PROTECTED] wrote:
I spose I could emit a broken-out.tar.gz file occasionally (it'd be up to 5
times a day), but there's no guarantee that it'll compile, let alone run.
I could also send a notification to mm-commits when I do so. Would that
help?
OK, I did that.
The
On Tue, 26 Jul 2005 14:41:49 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
Michael Krufky [EMAIL PROTECTED] wrote:
[ tracking mm stuff ]
Sigh, sorry. It's hard. -mm is always in flux. I no longer send out the
`patch was dropped' message because it disturbs people.
There were too
On Tue, 26 Jul 2005 15:32:51 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
Andrew Morton [EMAIL PROTECTED] wrote:
I spose I could emit a broken-out.tar.gz file occasionally (it'd be up to 5
times a day),
snip
OK, I did that.
Great!
The kernel.org propagation delay is a bit of a
Radoslaw AstralStorm Szkodzinski [EMAIL PROTECTED] wrote:
On Tue, 26 Jul 2005 14:41:49 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
Michael Krufky [EMAIL PROTECTED] wrote:
[ tracking mm stuff ]
Sigh, sorry. It's hard. -mm is always in flux. I no longer send out the
`patch
On Tue, 26 Jul 2005 16:11:49 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
All done - let me know if it needs anything else.
You got me with a tarball w/o a directory inside. Now I have to clean up the
mess.
Not the first time in life. I think I'll never learn. :)
--
AstralStorm
GPG Key
Radoslaw AstralStorm Szkodzinski [EMAIL PROTECTED] wrote:
On Tue, 26 Jul 2005 16:11:49 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
All done - let me know if it needs anything else.
You got me with a tarball w/o a directory inside. Now I have to clean up the
mess.
Not the first
On Tue, 26 Jul 2005 16:35:21 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
I did?
Exactly, I did untar it and I already had a directory called patches.
Of course cleaning it up took no time, as fortunately I had no patches with
exactly the same name and no series file in the directory above,
Andrew Morton said:
Radoslaw AstralStorm Szkodzinski [EMAIL PROTECTED] wrote:
On Tue, 26 Jul 2005 16:11:49 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
All done - let me know if it needs anything else.
You got me with a tarball w/o a directory inside. Now I have to clean
up the
Radoslaw AstralStorm Szkodzinski [EMAIL PROTECTED] wrote:
On Tue, 26 Jul 2005 16:35:21 -0700
Andrew Morton [EMAIL PROTECTED] wrote:
I did?
Exactly, I did untar it and I already had a directory called patches.
Of course cleaning it up took no time, as fortunately I had no patches
Andrew Morton wrote:
Michael Krufky [EMAIL PROTECTED] wrote:
[ tracking mm stuff ]
While we're on the topic of how -mm works, I have a question for you.
How can I test a kernel source tree (during compilation) to determine
whether it is a -mm tree or a -linus tree?
I will give you
Michael Krufky wrote:
However, sometimes there are patches in -mm that are incompatable with
-linus. An example of this is Pavel's pm_message_t mangling ...
Testing for the numbered 2.6.x version isn't enough of a test in a
case like this, but it would be nice to be able to develop against
Michael Krufky [EMAIL PROTECTED] wrote:
Andrew Morton wrote:
Michael Krufky [EMAIL PROTECTED] wrote:
[ tracking mm stuff ]
While we're on the topic of how -mm works, I have a question for you.
How can I test a kernel source tree (during compilation) to determine
whether
Andrew Morton wrote:
Michael Krufky [EMAIL PROTECTED] wrote:
However, sometimes there are patches in -mm that are incompatable with
-linus. An example of this is Pavel's pm_message_t mangling ...
OK. The way I handle an exceptional case like that is to merge the
-linus-compatible
38 matches
Mail list logo
