sm-commit AT lists.ibiblio.org
Subject: Source Mage code commit list
List archive
Re: [SM-Commit] GIT changes to master grimoire by Vlad Glagolev (0d786a2a05eaa6dbfa385cd3f98a05cfc5a35317)
- From: Ismael Luceno <ismael.luceno AT gmail.com>
- To: Vlad Glagolev <stealth AT sourcemage.org>
- Cc: sm-commit AT lists.ibiblio.org
- Subject: Re: [SM-Commit] GIT changes to master grimoire by Vlad Glagolev (0d786a2a05eaa6dbfa385cd3f98a05cfc5a35317)
- Date: Fri, 25 Dec 2015 03:48:18 -0200
On Wed, Dec 23, 2015 at 1:49 PM, Vlad Glagolev <scm AT sourcemage.org> wrote:
> GIT changes to master grimoire by Vlad Glagolev <stealth AT sourcemage.org>:
>
> devel/distcc/DETAILS | 4 ++--
> devel/distcc/HISTORY | 3 ---
> 2 files changed, 2 insertions(+), 5 deletions(-)
>
> New commits:
> commit 0d786a2a05eaa6dbfa385cd3f98a05cfc5a35317
> Author: Vlad Glagolev <stealth AT sourcemage.org>
> Commit: Vlad Glagolev <stealth AT sourcemage.org>
>
> Revert "distcc 3.2rc1"
>
> This reverts commit 86e85f984aea7e54a84f6e3e3b891245836a1109.
>
> Conflicts:
> devel/distcc/DETAILS
> devel/distcc/HISTORY
>
<...>
In this case, an exception to the rule should be made, 3.2rc1 is
already ancient, and there is 3 years of development between 3.1 and
3.2rc1.
The scenario calls for the release to be considered a normal one,
specially taking into account the development seems to have stopped
long ago.
Situations like this one call for special handling, and I also think
our rules regarding patches should be relaxed for these cases in order
to keep the spells useful. Although we should warn users, both
regarding spells not being actively maintained by upstream and
regarding patches to keep them working and safe.
-
[SM-Commit] GIT changes to master grimoire by Vlad Glagolev (0d786a2a05eaa6dbfa385cd3f98a05cfc5a35317),
Vlad Glagolev, 12/23/2015
- Re: [SM-Commit] GIT changes to master grimoire by Vlad Glagolev (0d786a2a05eaa6dbfa385cd3f98a05cfc5a35317), Ismael Luceno, 12/25/2015
Archive powered by MHonArc 2.6.24.