[mythtv] Ticket #4807: Save & use last tuned channel for entering LiveTV

Mark Buechler mark.buechler at gmail.com
Thu Aug 12 00:03:34 UTC 2010


On Wed, Aug 11, 2010 at 7:53 PM, Robert McNamara
<robert.mcnamara at gmail.com>wrote:

> On Wed, Aug 11, 2010 at 4:49 PM, Mark Buechler <mark.buechler at gmail.com>
> wrote:
> > On Wed, Aug 11, 2010 at 7:28 PM, MythTV <mythtv at cvs.mythtv.org> wrote:
> >>
> >> #4807: Save & use last tuned channel for entering LiveTV
> >>
> >>
> -----------------------------------------------------+----------------------
> >>  Reporter:  Mark Buechler <Mark.Buechler@…>          |           Owner:
> >>     Type:  patch                                    |          Status:
> >>  closed
> >>  Priority:  minor                                    |       Milestone:
> >>  unknown
> >> Component:  MythTV - DVB                             |         Version:
> >>  head
> >>  Severity:  medium                                   |      Resolution:
> >>  wontfix
> >>  Keywords:                                           |   Ticket locked:
>  0
> >>
> >>
> -----------------------------------------------------+----------------------
> >> Changes (by robertm):
> >>
> >>  * status:  new => closed
> >>  * resolution:  => wontfix
> >>
> >>
> >> Comment:
> >>
> >>  [TICKET CLEANUP]  Although I think this is a good idea, closing as it
> has
> >>  gone years without any attention.  I *do* think something like this
> >> should
> >>  get applied, so if you still feel strongly about it, please feel free
> to
> >>  open a new ticket with a patch against trunk.
> >>
> >> --
> >> Ticket URL: <http://svn.mythtv.org/trac/ticket/4807#comment:8>
> >> MythTV <http://www.mythtv.org/>
> >> MythTV
> >
> > <rant>
> > This is typical. I believe I've submitted maybe a dozen bug fix patches
> (all
> > very small) which have gotten committed, but every one of my feature
> patches
> > has been pushed since before 0.21 was out. One of mine was recently
> pushed
> > to 0.25 - and now this, probably my smallest, is classified 'wontfix'. I
> > COULD update the patch and resubmit, but I've tried that before - they
> never
> > got committed either, only to receive more requests to update against
> trunk
> > several months later.
> > Now, I really don't mean to complain, and in the past several years I've
> > waited for these to get looked at, I haven't. But after a while I really
> > have to wonder if it's worth my effort ever submitting a feature patch
> > again. Am I the only one in this boat? No, don't respond, you may find
> > yourself never seeing anything you write committed either.
> > </rant>
> > - Mark.
>
> Mark,
>
> I somewhat expected backlash, but unfortunately I just can't see any
> other way to get the ticket system cleaned up than to clean out
> patches that are so old as to have not been applicable in years.
> We're trying very hard to change the way we manage the ticketing
> system, but unfortunately that means making some tough decisions and
> possibly risking offense when we have to close some stale ones.  I am
> as frustrated as you are that this ticket has gone unheeded for so
> long, and so far it's the only one where I looked at it and said,
> "Man, I need to reimplement that for trunk."  So your point is well
> taken.  We just *have* to get to a point where there aren't 200
> tickets marked new, some of which are years old, so that we can
> properly triage tickets and handling things more promptly.
>
> For what it's worth, I'm trying to get all the tickets assigned so
> that "new" means something, and so that everyone has a personal
> accounting of their tickets, and so that we can get realistic
> milestones from people.
>
> Anyway, hope you can see both sides.
>
> Robert
> _______________________________________________
> mythtv-dev mailing list
> mythtv-dev at mythtv.org
> http://mythtv.org/cgi-bin/mailman/listinfo/mythtv-dev
>

I can, and thanks for the well thought out response. Like I said, this has
been years brewing for me I guess. I understand your point as well.

Maybe it would be worth while a document be created outlining coding style,
patch sizes and types expected to help make the process of review easier.
Things like separating major changes into separate patches, followed up
separately with whitespace cleanup - that sort of thing.

At some point I plan to update my very old tree, but in doing so I would
like to submit a series of patches. However, I won't bother if they either
won't get looked at or said features aren't wanted.

- Mark.

- Mark.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mythtv.org/pipermail/mythtv-dev/attachments/20100811/c98bc20f/attachment.htm>


More information about the mythtv-dev mailing list