[mythtv-users] [mythtv-commits] Ticket #5251: Add watched status as weighted input to Time/Priority auto expire

Phil Linttell phil.linttell at rogers.com
Wed Aug 11 20:28:54 UTC 2010


> Date: Wed, 11 Aug 2010 14:48:06 -0000
> From: "MythTV" <mythtv at cvs.mythtv.org>
> Subject: Re: [mythtv-commits] Ticket #5251: Add watched status as
> 	weighted input to Time/Priority auto expire
> Cc: mythtv-commits at mythtv.org
>
> #5251: Add watched status as weighted input to Time/Priority auto expire
> --------------------------------------+-------------------------------------
>  Reporter:  Nick French <naf@?>       |           Owner:  ijr    
>      Type:  enhancement               |          Status:  new    
>  Priority:  minor                     |       Milestone:  unknown
> Component:  MythTV - Scheduling       |         Version:  unknown
>  Severity:  medium                    |      Resolution:         
>  Keywords:                            |   Ticket locked:  0      
> --------------------------------------+-------------------------------------
>
> Comment (by databubble):
>
>  As of 25614, this patch no longer applies.... although it worked on builds
>  a month or so ago.
>
>  I've personally found it very useful for over a year...  I much prefer
>  items I've watched to be expired over items I haven't watched.  I don't
>  believe this is particularly intrustive.
>
>  Is there any chance it can be cleaned up and committed?
>
> -- Ticket URL: <http://svn.mythtv.org/trac/ticket/5251#comment:2>
> MythTV <http://www.mythtv.org/> MythTV ------------------------------
> Date: Wed, 11 Aug 2010 14:56:05 -0000 From: "MythTV"
> <mythtv at cvs.mythtv.org> Subject: Re: [mythtv-commits] Ticket #5251:
> Add watched status as weighted input to Time/Priority auto expire Cc:
> mythtv-commits at mythtv.org #5251: Add watched status as weighted input
> to Time/Priority auto expire
> --------------------------------------+-------------------------------------
> Reporter: Nick French <naf@?> | Owner: ijr Type: enhancement | Status:
> new Priority: minor | Milestone: unknown Component: MythTV -
> Scheduling | Version: unknown Severity: medium | Resolution: Keywords:
> | Ticket locked: 1
> --------------------------------------+-------------------------------------
> Changes (by robertm): * mlocked: 0 => 1 Comment: Please direct
> discussion to discussion lists. Ticket locked.

How does providing the valuable information that a patch no longer
applies, and querying it status, warrant the action of locking a
ticket?  By all means direct the discussion to the list, but don't lock
the ticket - someone might want to update the patch at make it useful
again.  You prefer multiple tickets?

Spending time and effort to test a patch, and then report back the
results against the ticket is, to me, the kind of  behaviour and
engagement the Project should encourage.  Locking the ticket as a reward
for their time and effort is like slapping them across the face with a
wet fish,



More information about the mythtv-users mailing list