* On 09 Apr 2013, Petr Pisar wrote:
> On Mon, Apr 08, 2013 at 03:31:19PM -0500, Derek Martin wrote:
> > As for the comment regarding the Mutt fork: in principle that's great,
> > but in practice IMO forks are bad: They divide the effort, and cause
> > problems potentially for both (or all) projec
On Mon, Apr 08, 2013 at 03:31:19PM -0500, Derek Martin wrote:
> As for the comment regarding the Mutt fork: in principle that's great,
> but in practice IMO forks are bad: They divide the effort, and cause
> problems potentially for both (or all) projects involved, trying to
> track important chan
#2842: reply_regexp set in muttrc and during mutt session have different effects
-+--
Reporter: gautam@…| Owner: mutt-dev
Type: defect | Status: closed
Priority: minor | Milestone:
Component: mutt|
* Kyle Wheeler [04-08-13 16:57]:
> On Monday, April 8 at 03:31 PM, quoth Derek Martin:
> >It's much easier to complain when something bugs you than it is to
> >remember to express appreciation when everything is fine...
>
> You know, that's an excellent point, and a good reminder. So:
>
> I wou
On Monday, April 8 at 03:31 PM, quoth Derek Martin:
It's much easier to complain when something bugs you than it is to
remember to express appreciation when everything is fine...
You know, that's an excellent point, and a good reminder. So:
I would like to profess that my copy of mutt has bee
Brendand,
On Fri, Apr 05, 2013 at 09:49:41AM -0700, Brendan Cully wrote:
> You're absolutely right. I and the other committers do not spend
> enough time on maintenance (we're all spread a lot thinner than we
> used to be, I think, and I don't see that changing in the short
> term). We know it's a
Michael Elkins wrote:
> The bug reporting system of full of open issues:
>
> http://dev.mutt.org/trac/report/1
>
> The problem is that it isn't very much fun to fix bugs, but writing
> a new feature that you would like is, so the few people who do
> submit patches tend to focus on that.
Alright,
On Mon, Apr 08, 2013 at 01:37:22PM -0500, Will Fiveash wrote:
It's never been clear to me who has the authorization to fix bugs or how
one acquires that authorization.
All you need to do is register for an account:
http://dev.mutt.org/trac/register
So far as I know, there are not special perm
On Mon, Apr 08, 2013 at 04:19:03PM +, Michael Elkins wrote:
>
> The bug reporting system of full of open issues:
>
> http://dev.mutt.org/trac/report/1
>
> The problem is that it isn't very much fun to fix bugs, but writing a new
> feature that you would like is, so the few people who do subm
On Sun, Apr 07, 2013 at 03:04:16PM +0100, Christian Ebert wrote:
Or, as Mutt is maintained in a Mercurial repo, to bitbucket.
Brendan mirrors the main repository to bitbucket:
https://bitbucket.org/mutt/mutt
On Fri, Apr 05, 2013 at 12:35:13PM -0700, Kevin J. McCarthy wrote:
I understand. More patches just means more work. The people who know
how to do things are too busy to do them, none-the-less mentor new
people. There certainly isn't an easy solution to this problem.
I would encourage mutt dev
11 matches
Mail list logo
