linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vincent Hanquez <tab@snarc.org>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: kernel versions on Linus bk tree
Date: Sat, 8 Jan 2005 20:00:22 +0100	[thread overview]
Message-ID: <20050108190022.GB8915@snarc.org> (raw)
In-Reply-To: <20050108185440.GA8915@snarc.org>

On Sat, Jan 08, 2005 at 07:54:40PM +0100, Vincent Hanquez wrote:
> > The problem is that 2.6.10 was released on kernel.org without the four
> > level change. But Linus bk which also has version 2.6.10 has the
> > change. Is there some way around this problem?
> 
> include/linux/version.h is generated by the Makefile. This file do not
> come with the source.

oops, I misread, just ignore the comment ;)
sorry for the noise.

-- 
Vincent Hanquez

  reply	other threads:[~2005-01-08 19:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-08 18:23 kernel versions on Linus bk tree Jon Smirl
2005-01-08 18:54 ` Vincent Hanquez
2005-01-08 19:00   ` Vincent Hanquez [this message]
2005-01-09  3:44 ` Horst von Brand
2005-01-10 22:26 ` Pavel Machek
2005-01-10 23:55 ` Ryan Anderson

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=20050108190022.GB8915@snarc.org \
    --to=tab@snarc.org \
    --cc=jonsmirl@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).