From: Andrew Morton <akpm@osdl.org>
To: Radoslaw "AstralStorm" Szkodzinski <astralstorm@gorzow.mm.pl>
Cc: mkrufky@m1k.net, linux-kernel@vger.kernel.org
Subject: Re: MM kernels - how to keep on the bleeding edge?
Date: Tue, 26 Jul 2005 16:11:49 -0700 [thread overview]
Message-ID: <20050726161149.0c9c36fa.akpm@osdl.org> (raw)
In-Reply-To: <20050727004932.1b25fc5d.astralstorm@gorzow.mm.pl>
Radoslaw "AstralStorm" Szkodzinski <astralstorm@gorzow.mm.pl> wrote:
>
> On Tue, 26 Jul 2005 14:41:49 -0700
> Andrew Morton <akpm@osdl.org> wrote:
>
> > Michael Krufky <mkrufky@m1k.net> 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 many?
> Or you were receiving a lot of mail from particular developers with
> requests of explanation? :)
I got lots of "waah, why did you drop my patch" from people whose patches
had been merged by Linus. Which is a bit odd given that those people were
previously cc'ed on the me->linus patch anyway. Ho hum. Adding a "why
this was dropped" to the email seemed too tricky.
> > The mm-commits
> > list does not resend a patch when it is changed (other patches folded into
> > it, rejects fixed, changelog updated, rediffed, etc).
>
> This isn't so much a problem as the previous point. When there are rejects,
> it's easy (most of the time) to fix them by hand anyway as I pull the tree.
>
> > Sometimes I'll comment out a patch but not fully drop it.
>
> Now I can see that, I can diff the series.
> But if the change was large, the diff isn't very instructive.
OK. I'm uploading the stripped series file at present (all the comments
are removed) because some versions of quilt don't like my new
comments-at-the-end-of-the-line feature. That actually breaks some of my
stuff too, so I'll probably stop using it ;)
> >
> > 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?
> >
>
> Really, it would. Especially if it contained an up-to-date series file.
> I'd be very grateful. (And would test and fix it up some more.)
All done - let me know if it needs anything else.
next prev parent reply other threads:[~2005-07-26 23:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 16:58 Radoslaw AstralStorm Szkodzinski
2005-07-26 19:45 ` Michael Krufky
2005-07-26 20:15 ` Radoslaw AstralStorm Szkodzinski
2005-07-26 20:26 ` Michael Krufky
2005-07-26 21:41 ` Andrew Morton
2005-07-26 22:32 ` Andrew Morton
2005-07-26 22:52 ` Radoslaw AstralStorm Szkodzinski
2005-07-26 22:49 ` Radoslaw AstralStorm Szkodzinski
2005-07-26 23:11 ` Andrew Morton [this message]
2005-07-26 23:25 ` Radoslaw AstralStorm Szkodzinski
2005-07-26 23:35 ` Andrew Morton
2005-07-26 23:54 ` Randy Dunlap
2005-07-27 0:00 ` Radoslaw AstralStorm Szkodzinski
2005-07-27 0:08 ` Andrew Morton
2005-07-30 2:39 ` Paul Jackson
2005-07-27 0:40 ` Michael Krufky
2005-07-27 1:02 ` Michael Krufky
2005-07-27 1:04 ` Andrew Morton
2005-07-27 1:13 ` Michael Krufky
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=20050726161149.0c9c36fa.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=astralstorm@gorzow.mm.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=mkrufky@m1k.net \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®