All of lore.kernel.org
 help / color / mirror / Atom feed
From: el es <el_es_cr@yahoo.co.uk>
To: linux-kernel@vger.kernel.org
Subject: Re: Kernel version : what about s.yy.ww.tt scheme ?
Date: Mon, 21 Jul 2008 07:57:03 +0000 (UTC)	[thread overview]
Message-ID: <loom.20080721T074322-56@post.gmane.org> (raw)
In-Reply-To: 20080720181426.GA29189@1wt.eu

Willy Tarreau <w <at> 1wt.eu> writes:


> 
> also, causes trouble when stable releases cross a year boundary, or
> when there are several ones in a week. The stable release should
> only be a counter, not a date.
> 
> Willy
> 
> 

If there are more stable releases in a week, you could put a release counter
after a dash, say : 2.08.30.40-[2...X]

If stable continues to be used and leaps over to next year, put another .yy.ww
section : 2.08.30.09.02

OK I know that's long, but easy to expand if needed, just be sure to separate
date pieces with dots and counters with dashes. Or...

maybe use them the other way round - the current scheme uses counters separated
by dots, so maybe the new could do ss.yy-ww-tt[[-yy]-ww][.X]] ? Like
2.08-30-40.2 ? 2.08-30-09-02.2 ? But this seems odd, even to me ;)

el es


  reply	other threads:[~2008-07-21  7:57 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-17  8:51 Kernel version : what about s.yy.ww.tt scheme ? el es
2008-07-17  9:48 ` Jan Engelhardt
2008-07-17 10:38   ` el es
2008-07-17 14:27     ` Justin Mattock
2008-07-18  9:12       ` Jan Engelhardt
2008-07-18 16:24         ` Justin Mattock
2008-07-20 18:14   ` Willy Tarreau
2008-07-21  7:57     ` el es [this message]
2008-07-21  9:18       ` david
2008-07-22 12:30         ` el es
2008-07-17 23:02 ` david
2008-07-18  8:31   ` el es
2008-07-18 15:24   ` Kernel version : what about YYYY.MM.[01].x ? Athanasius
2008-07-22 15:18     ` el es

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=loom.20080721T074322-56@post.gmane.org \
    --to=el_es_cr@yahoo.co.uk \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.