* Antonio Radici [20100109 15:43]:
> On Mon, Aug 03, 2009 at 11:47:07AM +0200, Gerfried Fuchs wrote:
> > ... this is a change that was introduced recently, what is the
> > rationale for that change? Why can't the old behavior stay? Changing
> > commandline handling in that way breaks backward com
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 ol
Hi :)
* Antonio Radici [2009-08-03 12:02:56 CEST]:
> On Mon, Aug 03, 2009 at 11:47:07AM +0200, Gerfried Fuchs wrote:
> > Would it be possible to revert that change to the old behavior?
>
> Hi Rhonda,
> unfortunately this change was introduced to have GNU getopt working as POSIX
> getopt
Hi,
you should at least provide a big warning when upgrading.
This little change just broke my server control system. cron catched the
error, but I think this might be very unhandy in some situations.
Why not first introduce a warning, that a behavior will change?
BTW: I'M not subscribed here, p
On Mon, Aug 03, 2009 at 11:47:07AM +0200, Gerfried Fuchs wrote:
> ... this is a change that was introduced recently, what is the
> rationale for that change? Why can't the old behavior stay? Changing
> commandline handling in that way breaks backward compatibility in a
> serious way and unfortunat
* Antonio Radici [2009-07-30 14:00:39 CEST]:
> On Thu, Jul 30, 2009 at 12:51:28PM +0200, Guido Günther wrote:
> > this broke with the recent upgrade:
> >
> > $ mutt -s bla -a .bashrc a...@sigxcpu.org < /dev/null
> > Can't stat a...@sigxcpu.org: No such file or directory
> > a...@sigxcpu.org: unab
On Thu, Jul 30, 2009 at 12:51:28PM +0200, Guido Günther wrote:
> Package: mutt
> Version: 1.5.20-2
> Severity: normal
>
> Hi,
> this broke with the recent upgrade:
>
> $ mutt -s bla -a .bashrc a...@sigxcpu.org < /dev/null
> Can't stat a...@sigxcpu.org: No such file or directory
> a...@sigxcpu.org
Package: mutt
Version: 1.5.20-2
Severity: normal
Hi,
this broke with the recent upgrade:
$ mutt -s bla -a .bashrc a...@sigxcpu.org < /dev/null
Can't stat a...@sigxcpu.org: No such file or directory
a...@sigxcpu.org: unable to attach file.
So mutt seems to skip the attachment name and tries to at
8 matches
Mail list logo
