From: Eduard-Gabriel Munteanu <maxdamage@aladin.ro>
To: linux-kernel@vger.kernel.org
Subject: Structure versioning
Date: Sat, 24 Jun 2006 16:39:48 +0000 [thread overview]
Message-ID: <449D6AD4.70202@aladin.ro> (raw)
*This message was transferred with a trial version of CommuniGate(r) Pro*
Wouldn't it be nice to keep a record of structs' revisions within
themselves? This might allow for very fast kernel update (if nothing
important hasn't changed between the two versions) with almost no
downtime. swsusp's state savers maybe aren't enough, but we can reuse
some code.
reply other threads:[~2006-06-24 13:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=449D6AD4.70202@aladin.ro \
--to=maxdamage@aladin.ro \
--cc=linux-kernel@vger.kernel.org \
/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