Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S267951AbUJJAwS (ORCPT ); Sat, 9 Oct 2004 20:52:18 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S267971AbUJJAwS (ORCPT ); Sat, 9 Oct 2004 20:52:18 -0400 Received: from rproxy.gmail.com ([64.233.170.197]:63985 "EHLO mproxy.gmail.com") by vger.kernel.org with ESMTP id S267951AbUJJAwR (ORCPT ); Sat, 9 Oct 2004 20:52:17 -0400 Message-ID: <9e47339104100917527993026d@mail.gmail.com> Date: Sat, 9 Oct 2004 20:52:16 -0400 From: Jon Smirl Reply-To: Jon Smirl To: Dave Airlie Subject: Re: [RFC] [patch] drm core internal versioning.. Cc: dri-devel@lists.sf.net, linux-kernel@vger.kernel.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 636 Lines: 19 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 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/