rlin / Berne /
Rome / Stockholm / Vienne
Objet: Re: [notmuch] Bug with commit 2e96464f9705be4ec772280cad71a6c9d5831e6f
On Sat, 16 Jan 2010 02:42:39 +0100 (CET), ra...@free.fr wrote:
> I still confirm the bug.
>
> The problem is due to relying on non-standardized fields of directory en
On Sat, 16 Jan 2010 02:42:39 +0100 (CET), ra...@free.fr wrote:
> I still confirm the bug.
>
> The problem is due to relying on non-standardized fields of directory entries
> (i.e. d_type), which don't behave the
> same on reiserfs than on ext2 (I use reiserfs).
>
> The following ugly patch "sol
x27;t known
what's the best way to go.
Matthieu
- Mail Original -
De: "Ali Polatel"
À: notmuch@notmuchmail.org
Envoyé: Mercredi 13 Janvier 2010 11h21:52 GMT +01:00 Amsterdam / Berlin / Berne
/ Rome / Stockholm / Vienne
Objet: Re: [notmuch] Bug with commit 2e96464f9705be
Ali Polatel yazmış:
> ra...@free.fr yazmış:
> > Hello,
> >
> > I just updated notmuch and now notmuch new cannot update my mail anymore...
> > It tells me that there are
> > 700 files found, but tells that there's no new mail.
> >
> > I did a git bisect, which tells me the first bad commit is co
On Mon, 11 Jan 2010 00:29:05 +0100 (CET), ra...@free.fr wrote:
> I just updated notmuch and now notmuch new cannot update my mail anymore...
> It tells me that there are
> 700 files found, but tells that there's no new mail.
Hi Mathieu,
Thanks for testing the new notmuch. I appreciate that. And
ra...@free.fr yazmış:
> Hello,
>
> I just updated notmuch and now notmuch new cannot update my mail anymore...
> It tells me that there are
> 700 files found, but tells that there's no new mail.
>
> I did a git bisect, which tells me the first bad commit is commit
> 2e96464f9705be4ec772280cad71
