On Fri, Aug 07, 2009 at 02:02:16PM +0200, Gerfried Fuchs wrote: > I wonder how many people really are on non-GNU systems and actually are > expecting this different behavior, and since when it is around. I > currently can't really find out when it was introduced, at least 1.5.13 > had still the old documentation, the documentation was adjusted for > 1.5.15, so the "feature" change would be probably be around since late > 2006/early 2007. >
Hi Rhonda, sorry for the late reply but I was a bit busy during last month; now the problem here is if we should roll back the upstream change or not, they will surely go ahead with their change because it is supporting both GNU and non-GNU systems. I know that it breaks an existing behavior but we didn't get many complaints so far, apart from three bug reports (including this one). As far as I understood, the patch was also covering Solaris, I know that we don't support Solaris but we should make sure that an user of that operating system or of any other GNU/non-GNU operating system could use the same version of mutt (1.5.19 in this case) w/out having different output or different options per distribution; what I care most is the user experience with this program and if we change the CLI options and stray from upstream that would mean that users from other distro will get a different experience once they start using Debian. Unfortunately, and this it really bad, we don't have numbers, so from my side this could be just a discussion and I can only try explain my opinion but I cannot quantify how many users are affected, how many are angry because we broke their scripts (actually, not "we", but "they" :-) ) and so on. I'd like to keep this behavior of mutt, if we do so I'm sure that we have to add a warning for people the mutt package (for example when squeeze goes out); I'm just wondering if my explanation makes sense to you or if you think that we should roll back their change. Thanks a lot for the discussion, it is being really helpful. Cheers Antonio -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
