Re: following 2.2.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 13 December 2001 12:35 pm, Ivan E. Moore II wrote: > On Thu, Dec 13, 2001 at 09:23:26PM +0200, Eray Ozkural (exa) wrote: > > On Thursday 13 December 2001 17:43, David Bishop wrote: > > > On Thursday 13 December 2001 08:40 am, Ivan E. Moore II wrote: > > > > yes. KDE_2_2_BRANCH is followed. > > > > > > Sweet, then I'll just wait for the next release of packages. Thanks! > > > > The branch won't last too long. There may not be another bugfix release. > > the branch will last until well after 3.0 is released. That, and the "releases" are mainly for the packagers sake: i.e., giving the packagers a snapshot to use as a reference. A stable branch like 2_2 should *always* be usable, and people are still rolling bugfixes and updates into it (hence my original question :-). So, to sum up, whether or not there is an official 2.2.3 or not is pretty irrelevant... - -- D.A.Bishop -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8GQ64EHLN/FXAbC0RAovaAKCcK1raK69ZZJvHVCfN2iVIrWW5AACfTCB3 kLfvDIepr83O77GUVZKsxAA= =tQa8 -END PGP SIGNATURE-
Re: following 2.2.2
On Thu, Dec 13, 2001 at 09:23:26PM +0200, Eray Ozkural (exa) wrote: > On Thursday 13 December 2001 17:43, David Bishop wrote: > > On Thursday 13 December 2001 08:40 am, Ivan E. Moore II wrote: > > > > > > yes. KDE_2_2_BRANCH is followed. > > > > Sweet, then I'll just wait for the next release of packages. Thanks! > > The branch won't last too long. There may not be another bugfix release. the branch will last until well after 3.0 is released. Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
Re: following 2.2.2
On Thursday 13 December 2001 17:43, David Bishop wrote: > On Thursday 13 December 2001 08:40 am, Ivan E. Moore II wrote: > > > > yes. KDE_2_2_BRANCH is followed. > > Sweet, then I'll just wait for the next release of packages. Thanks! The branch won't last too long. There may not be another bugfix release. -- Eray Ozkural (exa) <[EMAIL PROTECTED]> Comp. Sci. Dept., Bilkent University, Ankara www: http://www.cs.bilkent.edu.tr/~erayo GPG public key fingerprint: 360C 852F 88B0 A745 F31B EA0F 7C07 AE16 874D 539C
Re: following 2.2.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On Thursday 13 December 2001 08:40 am, Ivan E. Moore II wrote: > > Quick question, do the latest kde 2.2.2 packages use strictly > > KDE_2_2_RELEASE or KDE_2_2_BRANCH? There have been some bug fixes in > > _BRANCH that I would love to get my hands on, specifically (supposedly) a > > fix for the *long* standing "can't use an authenticating proxy with ssl" > > bug. > > yes. KDE_2_2_BRANCH is followed. Sweet, then I'll just wait for the next release of packages. Thanks! - -- D.A.Bishop -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8GMynEHLN/FXAbC0RAiNzAKCH9ks4oYRhAJBiruIQu2rKOybSRwCgmbPM FJDhBQZY3tsl6Wv+jwLIHts= =jys4 -END PGP SIGNATURE-
Re: following 2.2.2
> Quick question, do the latest kde 2.2.2 packages use strictly KDE_2_2_RELEASE > or KDE_2_2_BRANCH? There have been some bug fixes in _BRANCH that I would > love to get my hands on, specifically (supposedly) a fix for the *long* > standing "can't use an authenticating proxy with ssl" bug. yes. KDE_2_2_BRANCH is followed. Ivan -- Ivan E. Moore II [EMAIL PROTECTED] http://snowcrash.tdyc.com GPG KeyID=90BCE0DD GPG Fingerprint=F2FC 69FD 0DA0 4FB8 225E 27B6 7645 8141 90BC E0DD
following 2.2.2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Quick question, do the latest kde 2.2.2 packages use strictly KDE_2_2_RELEASE or KDE_2_2_BRANCH? There have been some bug fixes in _BRANCH that I would love to get my hands on, specifically (supposedly) a fix for the *long* standing "can't use an authenticating proxy with ssl" bug. Thanks. - -- D.A.Bishop -BEGIN PGP SIGNATURE- Version: GnuPG v1.0.6 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE8GMDCEHLN/FXAbC0RApQtAJ94XerHKeHcyTXMz+mHWT70iHWWNQCfaMKi 2MtSLehEiiAlophiDJv6hLQ= =je/5 -END PGP SIGNATURE-
