From: Pavel Machek <pavel@ucw.cz>
To: Stan Bubrouski <stan@ccs.neu.edu>
Cc: Patrick Mochel <mochel@osdl.org>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [pm] fix oops after saving image
Date: Sat, 4 Oct 2003 18:39:28 +0200 [thread overview]
Message-ID: <20031004163927.GA450@elf.ucw.cz> (raw)
In-Reply-To: <3F7EF4A0.7060504@ccs.neu.edu>
Hi!
> >>>+ * Note: The buffer we allocate to use to write the suspend header is
> >>>+ * not freed; its not needed since system is going down anyway
> >>>+ * (plus it causes oops and I'm lazy^H^H^H^Htoo busy).
> >>>+ */
> >>
> >>Too lazy to properly fix your comment as well.
> >
> >
> >Can you elaborate?
> > Pavel
>
> Pavel what mail client are you using? The last comment
> reads:
> + * (plus it causes oops and I'm lazy<CTRL-H><CTRL-H><CTRL-H><CTRL-H>too
> busy).
>
> I spelled out the ^H so you can see them, that is how
> the comment looks to me. The word 'lazy' is still in
> there along with too busy, you never backspaced over
> the lazy in the comment. That's all :P
:-))))))))))))))))))))))
No, my mail client is okay. I actually wrote ^ and H, and that should
be a joke.
Pavel
--
When do you have a heart between your knees?
[Johanka's followup: and *two* hearts?]
next prev parent reply other threads:[~2003-10-04 16:41 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-01 22:37 [pm] fix oops after saving image Pavel Machek
2003-10-02 16:40 ` Patrick Mochel
2003-10-02 20:39 ` Pavel Machek
2003-10-03 21:38 ` Patrick Mochel
2003-10-03 22:33 ` Pavel Machek
2003-10-04 5:17 ` Stan Bubrouski
2003-10-04 8:02 ` Pavel Machek
2003-10-04 7:50 ` Nigel Cunningham
2003-10-04 16:27 ` Stan Bubrouski
2003-10-04 16:26 ` Stan Bubrouski
2003-10-04 16:39 ` Pavel Machek [this message]
2003-10-04 16:53 ` Stan Bubrouski
2003-10-06 22:30 ` Patrick Mochel
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=20031004163927.GA450@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=mochel@osdl.org \
--cc=stan@ccs.neu.edu \
/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