Reply all - issue

Jameson Graef Rollins writes: > Just a thought: what if messages with a given tag (e.g. "new-thread") > were always treated as the source of a new thread? It's a good start. And an approach like that would have the advantage that one could undo a thread-split by just removing the tag. (That's

RE: Reply all - issue

Jameson Graef Rollins jroll...@finestructure.net writes: Just a thought: what if messages with a given tag (e.g. new-thread) were always treated as the source of a new thread? It's a good start. And an approach like that would have the advantage that one could undo a thread-split by just

Reply all - issue

On Wed, Jan 30 2013, David Bremner wrote: > Let me step back a level and say that special casing git patch series > strikes me as not yet seeing the problem in enough generality. Others > might disagree, of course. I agree with this statement. So I encounter the thread hijacking problem

RE: Reply all - issue

From many replies I understand manual thread-joining and -breaking exists with mutt's manual commands and default subject breaking -as Gmail does- would not be preferred, while not only version control systems vary subjects within a thread, but also discussions with slight off-topic forks and

RE: Reply all - issue

On Wed, Jan 30 2013, David Bremner da...@tethera.net wrote: Let me step back a level and say that special casing git patch series strikes me as not yet seeing the problem in enough generality. Others might disagree, of course. I agree with this statement. So I encounter the thread hijacking

Reply all - issue

>From many replies I understand manual thread-joining and -breaking exists with >mutt's manual commands and default subject breaking -as Gmail does- would not >be preferred, while not only version control systems vary subjects within a >thread, but also discussions with slight off-topic forks

Reply all - issue

Micha? Nazarewicz writes: > I was actually wondering that instead of hard coding the logic into notmuch > itself, maybe it would be better to provide some sort of "split-thread" and > "join-threads" which could than be used by separate tagging

Re: Reply all - issue

Michał Nazarewicz mina86-deaty8a+uhjqt0dzr+a...@public.gmane.org writes: I was actually wondering that instead of hard coding the logic into notmuch itself, maybe it would be better to provide some sort of split-thread and join-threads which could than be used by separate tagging tool. Such a

Reply all - issue

On Mon, Feb 04, 2013 at 11:39:44AM +0100, Micha? Nazarewicz wrote: > 2 lut 2013 17:21, "Robert Mast" napisa?(a): > > Anyone interested in me patching Notmuch, or shall I keep the changes to > myself? > > I was actually wondering that instead of hard coding the logic into notmuch > itself, maybe

Reply all - issue

2 lut 2013 17:21, "Robert Mast" napisa?(a): > So Gmail-threading is still the best I suppose, I strongly disagree. Having said that, as long as it's configurable I obviously won't be blocking your efforts. > Anyone interested in me patching Notmuch, or shall I keep the changes to myself? I was

RE: Reply all - issue

2 lut 2013 17:21, Robert Mast beheer...@tekenbeetziekten.nl napisał(a): So Gmail-threading is still the best I suppose, I strongly disagree. Having said that, as long as it's configurable I obviously won't be blocking your efforts. Anyone interested in me patching Notmuch, or shall I keep the

Re: Reply all - issue

On Mon, Feb 04, 2013 at 11:39:44AM +0100, Michał Nazarewicz wrote: 2 lut 2013 17:21, Robert Mast beheer...@tekenbeetziekten.nl napisał(a): Anyone interested in me patching Notmuch, or shall I keep the changes to myself? I was actually wondering that instead of hard coding the logic into

Reply all - issue

CC: notmuch at notmuchmail.org Onderwerp: [Spam-verdenking][english 100%] RE: Reply all - issue Robert Mast writes: > > Anyone interested in me patching Notmuch, or shall I keep the changes > to myself? > Hi Robert; If you have patches, and you want feedback on them, then you a

Reply all - issue

Robert Mast writes: > I committed a little patch on a memory-issue I found. Where did you commit it? > > Can someone look whether I used git the right way, or should I study > git send-email some further? I guess that's probably the simplest. Otherwise you need to push it to a publically

[Spam-verdenking][english 100%] RE: Reply all - issue

][english 100%] RE: Reply all - issue Robert Mast writes: > > Anyone interested in me patching Notmuch, or shall I keep the changes > to myself? > Hi Robert; If you have patches, and you want feedback on them, then you are of course welcome to send them to the list. Previous experie

RE: Reply all - issue

: notmuch@notmuchmail.org Onderwerp: [Spam-verdenking][english 100%] RE: Reply all - issue Robert Mast beheer...@tekenbeetziekten.nl writes: Anyone interested in me patching Notmuch, or shall I keep the changes to myself? Hi Robert; If you have patches, and you want feedback on them, then you

RE: Reply all - issue

Robert Mast beheer...@tekenbeetziekten.nl writes: I committed a little patch on a memory-issue I found. Where did you commit it? Can someone look whether I used git the right way, or should I study git send-email some further? I guess that's probably the simplest. Otherwise you need to

Reply all - issue

Off course I?ll try not to hinder the current notmuch-users. My intent is to even find some support for it. As far as I know Gmail was the great example of threading for the SUP-developers, and SUP lead to Notmuch. So Gmail-threading is still the best I suppose, except for git

Reply all - issue

Robert Mast writes: > > Anyone interested in me patching Notmuch, or shall I keep the changes > to myself? > Hi Robert; If you have patches, and you want feedback on them, then you are of course welcome to send them to the list. Previous experience suggests us that it is often faster in the

RE: Reply all - issue

Off course I’ll try not to hinder the current notmuch-users. My intent is to even find some support for it. As far as I know Gmail was the great example of threading for the SUP-developers, and SUP lead to Notmuch. So Gmail-threading is still the best I suppose, except for git

RE: Reply all - issue

Robert Mast beheer...@tekenbeetziekten.nl writes: Anyone interested in me patching Notmuch, or shall I keep the changes to myself? Hi Robert; If you have patches, and you want feedback on them, then you are of course welcome to send them to the list. Previous experience suggests us that it

RE: [Spam-verdenking][english 100%] RE: Reply all - issue

][english 100%] RE: Reply all - issue Robert Mast beheer...@tekenbeetziekten.nl writes: Anyone interested in me patching Notmuch, or shall I keep the changes to myself? Hi Robert; If you have patches, and you want feedback on them, then you are of course welcome to send them to the list

Reply all - issue

On Mi, 30 ian 13, 22:39:40, Suvayu Ali wrote: > > That said, I think this feature is indeed useful at times but it should > be implemented in the UI on user command or as a configurable (e.g. mutt > provides the command), not a default underlying behaviour > of the backend. If this is pursued,

Reply all - issue

28 sty 2013 08:37, "Robert Mast" napisa?(a): > I think of a fix that indexes the first dates of (stripped) subject-changes within threads, and with each first (stripped) subject change check the body on quotes of previous messages. If there is no quote to referenced mails then drop the reference

Re: Reply all - issue

On Mi, 30 ian 13, 22:39:40, Suvayu Ali wrote: That said, I think this feature is indeed useful at times but it should be implemented in the UI on user command or as a configurable (e.g. mutt provides the break-thread command), not a default underlying behaviour of the backend. If this is

Re: Reply all - issue

28 sty 2013 08:37, Robert Mast beheer...@tekenbeetziekten.nl napisał(a): I think of a fix that indexes the first dates of (stripped) subject-changes within threads, and with each first (stripped) subject change check the body on quotes of previous messages. If there is no quote to referenced

Reply all - issue

:beheerder at tekenbeetziekten.nl] Verzonden: woensdag 30 januari 2013 21:57 Aan: 'Carl Worth'; 'Jani Nikula'; 'notmuch at notmuchmail.org' Onderwerp: RE: Reply all - issue I never used git for mailpatching, so I have no example-mailbox to analyse. I understand that the subject starting with "[PATCH

Reply all - issue

Hi, I am a *very new* notmuch user (notmuch + mutt-kz/Emacs), but I would like to throw in a few opinions about this topic. On Wed, Jan 30, 2013 at 06:14:48PM +0100, Robert Mast wrote: > Thanks for your clear explanation. > > The thread-merging and breaking is in the procedure already pointed

Reply all - issue

ailto:beheerder at tekenbeetziekten.nl] Verzonden: woensdag 30 januari 2013 18:15 Aan: 'Carl Worth'; 'Jani Nikula'; 'notmuch at notmuchmail.org' Onderwerp: RE: Reply all - issue Thanks for your clear explanation. The thread-merging and breaking is in the procedure already pointed at by Jani: (_

Reply all - issue

David Bremner writes: > > Hardcoding particular headers sounds too fragile to me. With that said, > if you want a corpus of email to investigate, there is e.g. > Let me step back a level and say that special casing git patch series strikes me as not yet seeing the problem in enough generality.

Reply all - issue

Robert Mast writes: > I ran git send-email and became the following line in the mail-header: > > "X-Mailer: git-send-email 1.7.9.5" > > Can I assume, apart from the version number, that this header-marker applies > to all git-mail that should not be subject-splitted? Hardcoding particular

Reply all - issue

-breaking? -Oorspronkelijk bericht- Van: Carl Worth [mailto:cworth at cworth.org] Verzonden: dinsdag 29 januari 2013 3:48 Aan: Robert Mast; 'Jani Nikula'; notmuch at notmuchmail.org Onderwerp: RE: Reply all - issue Is there any existing thread-breaking? There wasn't the last time I

RE: Reply all - issue

-breaking? -Oorspronkelijk bericht- Van: Carl Worth [mailto:cwo...@cworth.org] Verzonden: dinsdag 29 januari 2013 3:48 Aan: Robert Mast; 'Jani Nikula'; notmuch@notmuchmail.org Onderwerp: RE: Reply all - issue Is there any existing thread-breaking? There wasn't the last time I looked

RE: Reply all - issue

30 januari 2013 18:15 Aan: 'Carl Worth'; 'Jani Nikula'; 'notmuch@notmuchmail.org' Onderwerp: RE: Reply all - issue Thanks for your clear explanation. The thread-merging and breaking is in the procedure already pointed at by Jani: (_notmuch_database_link_message() in lib/database.cc

Re: Reply all - issue

Hi, I am a *very new* notmuch user (notmuch + mutt-kz/Emacs), but I would like to throw in a few opinions about this topic. On Wed, Jan 30, 2013 at 06:14:48PM +0100, Robert Mast wrote: Thanks for your clear explanation. The thread-merging and breaking is in the procedure already pointed at

RE: Reply all - issue

...@tekenbeetziekten.nl] Verzonden: woensdag 30 januari 2013 21:57 Aan: 'Carl Worth'; 'Jani Nikula'; 'notmuch@notmuchmail.org' Onderwerp: RE: Reply all - issue I never used git for mailpatching, so I have no example-mailbox to analyse. I understand that the subject starting with [PATCH anything] can be a git

RE: Reply all - issue

Robert Mast beheer...@tekenbeetziekten.nl writes: I ran git send-email and became the following line in the mail-header: X-Mailer: git-send-email 1.7.9.5 Can I assume, apart from the version number, that this header-marker applies to all git-mail that should not be subject-splitted?

RE: Reply all - issue

David Bremner da...@tethera.net writes: Hardcoding particular headers sounds too fragile to me. With that said, if you want a corpus of email to investigate, there is e.g. Let me step back a level and say that special casing git patch series strikes me as not yet seeing the problem in enough

Reply all - issue

Robert Mast writes: > Your point on patch-breaking related to gmail and my proposal isn't > completely clear to me, but I've probably addressed it well with my new > approach. The issue here is that many developers tend to develop a patch series (perhaps with dozens of patches) as a single

Reply all - issue

Thanks for your reply. I never tried gmail-conversation threading, but from your first reference I understand it breaks threads on subject unconditionally. Breaking on subject unconditionally would be even easier to implement, as comparing the contents of previous messages takes performance and

Reply all - issue

On Sun, 27 Jan 2013, Robert Mast wrote: > Last week I studied many Windows-Mail User Agents with the conversation > threading feature. > > None of them (SUP, mutt-kz(notmuch), Outlook 2010, Thunderbird with > conversation thread plug in, Postbox, Evolution) could cope with the > following case:

Re: Reply all - issue

On Sun, 27 Jan 2013, Robert Mast beheer...@tekenbeetziekten.nl wrote: Last week I studied many Windows-Mail User Agents with the conversation threading feature. None of them (SUP, mutt-kz(notmuch), Outlook 2010, Thunderbird with conversation thread plug in, Postbox, Evolution) could cope with

RE: Reply all - issue

Thanks for your reply. I never tried gmail-conversation threading, but from your first reference I understand it breaks threads on subject unconditionally. Breaking on subject unconditionally would be even easier to implement, as comparing the contents of previous messages takes performance and

RE: Reply all - issue

Robert Mast beheer...@tekenbeetziekten.nl writes: Your point on patch-breaking related to gmail and my proposal isn't completely clear to me, but I've probably addressed it well with my new approach. The issue here is that many developers tend to develop a patch series (perhaps with dozens of

Reply all - issue

Last week I studied many Windows-Mail User Agents with the conversation threading feature. None of them (SUP, mutt-kz(notmuch), Outlook 2010, Thunderbird with conversation thread plug in, Postbox, Evolution) could cope with the following case: In our e-mail-discussions people often choose

Reply all - issue

Last week I studied many Windows-Mail User Agents with the conversation threading feature. None of them (SUP, mutt-kz(notmuch), Outlook 2010, Thunderbird with conversation thread plug in, Postbox, Evolution) could cope with the following case: In our e-mail-discussions people often choose