From: Florian Weimer <fw@deneb.enyo.de>
Subject: Re: Oort Release Schedule
Date: Sat, 12 Jan 2002 12:35:43 +0100 [thread overview]
Message-ID: <87advj94z4.fsf@deneb.enyo.de> (raw)
In-Reply-To: <m3y9j4qsy6.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 12 Jan 2002 02:05:53 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> One nice thing about numbered updates (ognus-0.45.tar.gz) is that you
> can see which version the user is actually using.
Somebody could set up a daily cron job which automatically commits a
new version number every day. ;-)
next prev parent reply other threads:[~2002-01-12 11:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-12 1:05 Lars Magne Ingebrigtsen
2002-01-12 10:12 ` Frank Schmitt
2002-01-12 11:05 ` Lars Magne Ingebrigtsen
2002-01-12 21:44 ` Steinar Bang
2002-01-12 22:21 ` Lars Magne Ingebrigtsen
2002-01-12 22:57 ` Simon Josefsson
2002-01-12 23:10 ` Lars Magne Ingebrigtsen
2002-01-13 9:16 ` Pavel Janík
2002-01-13 10:00 ` Andreas Fuchs
2002-01-13 11:54 ` Lars Magne Ingebrigtsen
2002-01-12 11:35 ` Florian Weimer [this message]
2002-01-13 18:13 ` Manoj Srivastava
2002-01-14 20:21 ` Steinar Bang
2002-01-16 2:53 ` Lars Magne Ingebrigtsen
2002-01-18 7:04 ` Manoj Srivastava
2002-01-14 12:33 ` Christoph Rohland
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=87advj94z4.fsf@deneb.enyo.de \
--to=fw@deneb.enyo.de \
/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).