From: Jon Smirl <jonsmirl@gmail.com>
To: Dave Airlie <airlied@linux.ie>
Cc: dri-devel@lists.sf.net, linux-kernel@vger.kernel.org
Subject: Re: [RFC] [patch] drm core internal versioning..
Date: Sat, 9 Oct 2004 20:52:16 -0400 [thread overview]
Message-ID: <9e47339104100917527993026d@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0410100050160.6083@skynet>
How strong of match requirement do we need? Note that this only
impacts distribution of binary personality modules, if you have source
there is no problem.
Several stronger solutions:
on each CVS check-in to DRM increment a count and use this for an id
manual version number for DRM
embed the kernel version
embed the kernel version plus distribution info
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2004-10-10 0:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-09 23:54 [RFC] [patch] drm core internal versioning Dave Airlie
2004-10-10 0:52 ` Jon Smirl [this message]
2004-10-10 2:31 ` Dave Airlie
2004-10-10 4:29 ` Greg KH
2004-10-10 5:30 ` Dave Airlie
2004-10-10 6:44 ` Arjan van de Ven
2004-10-10 7:00 ` Dave Airlie
2004-10-12 1:46 ` Ian Romanick
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=9e47339104100917527993026d@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=airlied@linux.ie \
--cc=dri-devel@lists.sf.net \
--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