[PATCH] Re: Prepare dynamic plugins (again)
[Top] [All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
( re-adding the mailing list to the cc list, plus a bit more comments )
On Wed, Sep 09, 2009 at 03:55:37PM +0200, Christoph Höger wrote:
> Am Mittwoch, den 09.09.2009, 15:03 +0200 schrieb Nicolas Sebrecht:
> > On Tue, Sep 08, 2009 at 09:52:21AM -0500, John Goerzen wrote:
> > >
> > > Christoph Höger wrote:
> > > > Here we go again, this time much smaller and without the
> > > > GnomeUI.
> > >
> > > Something corrupted this; don't know if it was Ecartis or something
> > > else. Can you try sending again, directly to my email address this time?
> >
> > Christoph, cc me please (if not already done).
> >
> > If I come too late, could you please give feedback to the list? I'm
> > pretty sure mutt is to blame here but this test is a good idea.
> >
> > It is fustrating to know that a patch can't be reviewed and merged only
> > because of a corruption in the mail chain.
>
> Done. I've sent it to you. I guess the latest corruption was mutts
> mis-detection of utf-8 (it set iso-8859-15 in the header).
It could really be that. The patch sent directly to me is fine, but the
charset is set to utf8 too. So I'm unable to say if the problem comes
from mutt or Ecartis.
> But again, I
> am wondering why sending directly to me, saving as mailbox and applying
> works fine ...
I'm not sure but denpending of what kind of "saving as mailbox"
operation you do and configuration you have, mutt may decode the mail
while saving.
> Btw: I would use git-send-email, but that tool seems not to exist
> anymore in git 1.6
I'm sure send-email exists in the whole 1.6 series of Git. I do follow
the development of Git and I use the "unreleased yet" next branch. Do
you use the vanilla git from an official repository or a package from
your linux distribution. Or maybe a port of Git to another OS?
--
Nicolas Sebrecht
[PATCH] Prepare dynamic plugins (again), Christoph Höger, 2009/09/09
|
|