On Wed, Mar 17, 2010 at 4:39 PM, Karl Fogel <email address hidden> wrote:
> Brian, thanks. I think the best course is probably not to do anything
> about it until someone says "I can't see the patches" or something,
> anyway. It's just when the subscribers or "also notified" list is
> really long, it takes up a lot of real estate. There are other possible
> solutions: contractable list, etc. Just thinking out loud.
I agree with this course of action. However, I'm keen to know what
kind of workflows require looking at the subscriber list. Separate
discussion, I guess.
On Wed, Mar 17, 2010 at 4:39 PM, Karl Fogel <email address hidden> wrote:
> Brian, thanks. I think the best course is probably not to do anything
> about it until someone says "I can't see the patches" or something,
> anyway. It's just when the subscribers or "also notified" list is
> really long, it takes up a lot of real estate. There are other possible
> solutions: contractable list, etc. Just thinking out loud.
I agree with this course of action. However, I'm keen to know what
kind of workflows require looking at the subscriber list. Separate
discussion, I guess.
jml