From: Pavel Machek <pavel@ucw.cz>
To: Johannes Berg <johannes@sipsolutions.net>
Cc: Pekka J Enberg <penberg@cs.helsinki.fi>,
linux-pm@lists.osdl.org, nigel@nigel.suspend2.net
Subject: Re: Re: [RFC/PATCH 2/2] kernel: don't update load average during snapshot/shutdown
Date: Fri, 27 Apr 2007 17:14:49 +0200 [thread overview]
Message-ID: <20070427151449.GS22250@elf.ucw.cz> (raw)
In-Reply-To: <1177686732.3565.30.camel@johannes.berg>
Hi!
> > I think we should track -mm for now. git tree means Linus has to
> > trust you, and if he does not, you are in _big_ trouble.
>
> We could still generate patches from the actual git tree and send those
> on to -mm. Bit more work though. Dunno. I try to import patches I
> > see on
git history generates "bad" patches for merging. If you merge foo,
then do two fixups, it is three patches; very nasty to review.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2007-04-27 15:14 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-27 13:29 [RFC/PATCH 2/2] kernel: don't update load average during snapshot/shutdown Pekka J Enberg
2007-04-27 14:52 ` Pavel Machek
2007-04-27 14:55 ` Pekka Enberg
2007-04-27 21:32 ` Nigel Cunningham
2007-04-27 22:12 ` Pavel Machek
2007-04-27 22:18 ` Nigel Cunningham
2007-04-27 22:25 ` Pavel Machek
2007-04-27 23:05 ` Nigel Cunningham
2007-04-28 8:01 ` Pavel Machek
2007-04-28 8:26 ` Pekka Enberg
2007-04-28 10:49 ` Rafael J. Wysocki
2007-04-28 18:07 ` Rafael J. Wysocki
2007-04-28 22:52 ` Nigel Cunningham
2007-04-27 15:00 ` Rafael J. Wysocki
2007-04-27 14:59 ` Pekka Enberg
2007-04-27 15:31 ` Rafael J. Wysocki
2007-04-27 15:02 ` Johannes Berg
2007-04-27 15:05 ` Pavel Machek
2007-04-27 15:12 ` Johannes Berg
2007-04-27 15:14 ` Pavel Machek [this message]
2007-04-27 15:53 ` Rafael J. Wysocki
2007-04-27 19:56 ` Johannes Berg
2007-04-27 15:16 ` Gautham R Shenoy
2007-04-27 15:30 ` Rafael J. Wysocki
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=20070427151449.GS22250@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=johannes@sipsolutions.net \
--cc=linux-pm@lists.osdl.org \
--cc=nigel@nigel.suspend2.net \
--cc=penberg@cs.helsinki.fi \
/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