From: Stas Sergeev <stsp@aknet.ru>
To: linux-msdos@vger.kernel.org
Subject: Re: Stabilisation of 1.3.2?
Date: Wed, 26 Oct 2005 21:05:06 +0400 [thread overview]
Message-ID: <435FB742.9020909@aknet.ru> (raw)
Hello.
Mgr. Peter Tuharsky wrote:
> I'd like to ask anybody competent, if 1.3.2 couldn't be stabilised.
Of course it can be. 1.3.2 had some nasty things
inside, but now most of its PRs were resolved, so
I'd say it had quite stabilized.
> It has been here for a while, poeople need it's features, and I simply
> feel it's time to "move on" ;o)
What do you mean by "move on"? If you have the
particular list of the new features you'd like to
see added - feel free to make that list available.
If you just want to move on by following the project
development - cvs is your friend, and you can follow
the code progress very closely. The project *is*
moving on, and it had advanced since 1.3.2 too. It
just depends on the one's particular needs whether
or not it moves on for him. It is even possible for
everyone to influence the direction, so if you feel
like it's time to move on - then go ahead! :)
next reply other threads:[~2005-10-26 17:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-26 17:05 Stas Sergeev [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-10-26 6:17 Stabilisation of 1.3.2? Mgr. Peter Tuharsky
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=435FB742.9020909@aknet.ru \
--to=stsp@aknet.ru \
--cc=linux-msdos@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.