At this point there's not much of my original code left. :D Don, you're
welcome to take the credit in the commit.
On Wed, Apr 3, 2024, 9:46 AM Don Porter wrote:
> From: Austin Clements
>
> The E1000 debug messages are very useful for developing drivers.
> Make these avai
Jan, assuming you're running on an AMD CPU, this is go.dev/issue/34988 (if
you're not running on an AMD CPU, that would be very interesting to know!)
The TL;DR is that this appears to be a kernel bug, and we have a C
reproducer, but we do not yet have a fix or a workaround.
On Wed, Dec 15, 2021 a
Thanks for that data point, Nick. It's a good idea to make the build fail
if GO386 is set to 387 if we drop support. It already fails if GO386 is set
to any unsupported value, but we could continue to check GO386 even though
there would only be one supported value, and perhaps give a nicer error if
Hi everyone. We’re exploring the possibility of dropping 387 floating-point
support and requiring SSE2 support for GOARCH=386 in the native gc
compiler, potentially in Go 1.16. This would raise the minimum GOARCH=386
requirement to the Intel Pentium 4 (released in 2000) or AMD Opteron/Athlon
64 (re
runs on that limits the map count.
We've seen one other application experience VSS growth with the 1.12
changes, and it does seem to require a pretty unique allocation pattern.
Michael (cc'd) may be zeroing in on the causes of this and may have some
patches for you to try if you don't min
Acquiring a mutex while pinned can cause deadlock because pinning prevents
a stop-the-world. For example, the following sequence could result in a
deadlock:
M1: Acquires mutex l.
M2: Pins the M.
M2: Attempts to acquire mutex l.
M3: Initiates stop-the-world
M3: Stops M1
M3: Attempts to stop M2, but
Hi Rémy. We often fight with vm.max_map_count in the runtime, sadly. Most
likely this comes from the way the runtime interacts with Linux's
transparent huge page support. When we scavenge (release to the OS) only
part of a huge page, we tell the OS not to turn that huge page frame back
into a huge
AFAIK, the only thing that can cause this in Go 1.8 is a non-preemptible
loop. It's not related to the heap size at all.
To test this theory, you can set GOEXPERIMENT=preemptibleloops and rebuild
your Go tree (the compiler has to be built with this, so you can't just
turn it on to build your proje
On Tue, Nov 29, 2016 at 6:57 PM, Rick Hudson wrote:
> That is correct.
... but not guaranteed. :)
--
You received this message because you are subscribed to the Google Groups
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to golang-nuts+
Quoth David Bremner on Nov 04 at 1:26 pm:
>
> Paul Wise wrote:
>
> > Last night I got this error from my `notmuch new --quiet` cron job. The
> > file that the error message complains about is now in the cur directory
> > of the maildir at the following path.
> >
> > /path/to/mail/cur/1478190211.
Quoth David Bremner on Nov 04 at 1:26 pm:
>
> Paul Wise wrote:
>
> > Last night I got this error from my `notmuch new --quiet` cron job. The
> > file that the error message complains about is now in the cur directory
> > of the maildir at the following path.
> >
> > /path/to/mail/cur/1478190211.
PSA: This may be related to a broken headphone jack that is supposed to
detect whether headphones are plugged in and change output accordingly.
Work around in ubuntu right now is to run alsamixer from terminal,
select correct soundcard, then disable auto-mute, then unmute and turn
up speakers.
--
PSA: This may be related to a broken headphone jack that is supposed to
detect whether headphones are plugged in and change output accordingly.
Work around in ubuntu right now is to run alsamixer from terminal,
select correct soundcard, then disable auto-mute, then unmute and turn
up speakers.
--
PSA: This may be related to a broken headphone jack that is supposed to
detect whether headphones are plugged in and change output accordingly.
Work around in ubuntu right now is to run alsamixer from terminal,
select correct soundcard, then disable auto-mute, then unmute and turn
up speakers.
--
Public bug reported:
Under sound settings only headphone output is listed as an option, no
internal speakers are listed. Headphone playback does work. In
alsamixer, speaker output was at 0 and muted, but unmuting and
increasing volume does not produce playback in speakers.
ASUS X550LB laptop
Pro
Public bug reported:
Under sound settings only headphone output is listed as an option, no
internal speakers are listed. Headphone playback does work. In
alsamixer, speaker output was at 0 and muted, but unmuting and
increasing volume does not produce playback in speakers.
ASUS X550LB laptop
Pro
Public bug reported:
Under sound settings only headphone output is listed as an option, no
internal speakers are listed. Headphone playback does work. In
alsamixer, speaker output was at 0 and muted, but unmuting and
increasing volume does not produce playback in speakers.
ASUS X550LB laptop
Pro
-base is certainly helpful here.
To more directly answer your questions, though, I proposed
https://github.com/golang/go/issues/13463#issuecomment-235048896 a while
ago (not yet implemented or necessarily agreed upon). I think this
extension to the heap proflie would answer your questions without
I think what you're seeing is simply rounding in the values printed by the
gctrace. You're correct that the two metrics are reporting the same thing.
In fact, they come from the exact same time stamps internally. But
formatting floating point numbers is hard. :) The gctrace printer simply
truncates
Quoth Gaute Hope on Jun 06 at 8:08 pm:
> Austin Clements writes on juni 6, 2016 21:20:
> >
> >The experiment was specifically for regexp matching subject, but it should
> >work for any header we store a literal copy of in the database.
>
> Does it work for terms in t
On Mon, Jun 6, 2016 at 1:29 PM, David Bremner wrote:
> Sebastian Fischmeister writes:
>
> >
> > I ran into this problem before as well. Storage is cheap. Notmuch could
> > index all emails with reversed text to get around some of this
> > problem. It doesn't solve the problem of *analysis*, but
On Mon, 11 Apr 2016, Daniel Kahn Gillmor wrote:
> On Sun 2016-04-10 20:33:02 -0400, David Bremner wrote:
>> Daniel Kahn Gillmor writes:
>>
>>> To fully complete the ghost-on-removal-when-shared-thread-exists
>>> proposal, we need to clear all ghost messages when the last active
>>> message is re
Hi David. I haven't had a chance to look back at the original code, but
your follow-up expanded comment agrees with how I remember this code
working.
On Aug 7, 2015 4:41 PM, "David Bremner" wrote:
> Daniel Schoepe writes:
>
>
> > On Fri, 05 Jun 2015 19:28 +0200, David Bremner wrote:
> >> +
Hi David. I haven't had a chance to look back at the original code, but
your follow-up expanded comment agrees with how I remember this code
working.
On Aug 7, 2015 4:41 PM, "David Bremner" wrote:
> Daniel Schoepe writes:
>
>
> > On Fri, 05 Jun 2015 19:28 +0200, David Bremner wrote:
> >> +
Hi Xu. I may be misunderstanding your email, but it sounds like you want to
know if a message has *any* reply message. That's not what the replied tag
indicates. The replied tag indicates that *you* have sent a reply to a message.
Mechanically, when you hit, say, r to start a reply and then send
Hi Xu. I may be misunderstanding your email, but it sounds like you want to
know if a message has *any* reply message. That's not what the replied tag
indicates. The replied tag indicates that *you* have sent a reply to a message.
Mechanically, when you hit, say, r to start a reply and then send
Quoth Ronny Chevalier on Apr 22 at 4:01 am:
> On Wed, Apr 22, 2015 at 3:28 AM, Austin Clements
> wrote:
> > On Tue, 21 Apr 2015, Ronny Chevalier wrote:
> >> On Tue, Apr 21, 2015 at 1:35 AM, David Bremner
> >> wrote:
> >>> Ronny Chevalier writes:
>
On Tue, 21 Apr 2015, Ronny Chevalier wrote:
> On Tue, Apr 21, 2015 at 1:35 AM, David Bremner wrote:
>> Ronny Chevalier writes:
> Austin Clements wrote:
>> And I think there's a fairly easy way to do it in C code that will
>> also prevent library interface bloa
Quoth Ronny Chevalier on Apr 22 at 4:01 am:
> On Wed, Apr 22, 2015 at 3:28 AM, Austin Clements
> wrote:
> > On Tue, 21 Apr 2015, Ronny Chevalier wrote:
> >> On Tue, Apr 21, 2015 at 1:35 AM, David Bremner wrote:
> >>> Ronny Chevalier writes:
> >>
On Tue, 21 Apr 2015, Ronny Chevalier wrote:
> On Tue, Apr 21, 2015 at 1:35 AM, David Bremner wrote:
>> Ronny Chevalier writes:
> Austin Clements wrote:
>> And I think there's a fairly easy way to do it in C code that will
>> also prevent library interface bloa
Quoth Scott Kitterman on Mar 28 at 5:36 pm:
> On Sunday, March 15, 2015 12:43:51 PM Scott Kitterman wrote:
> > I've poked around in core/libs/database/collectionmanager.cpp and it appears
> > that the digikam code tries to do the right thing and the most likely issue
> > is something about how sol
Quoth Scott Kitterman on Mar 28 at 5:36 pm:
> On Sunday, March 15, 2015 12:43:51 PM Scott Kitterman wrote:
> > I've poked around in core/libs/database/collectionmanager.cpp and it appears
> > that the digikam code tries to do the right thing and the most likely issue
> > is something about how sol
Quoth Scott Kitterman on Mar 28 at 5:36 pm:
> On Sunday, March 15, 2015 12:43:51 PM Scott Kitterman wrote:
> > I've poked around in core/libs/database/collectionmanager.cpp and it appears
> > that the digikam code tries to do the right thing and the most likely issue
> > is something about how sol
shr has really nice support for inline image rendering, but previously
we only had the hooks for w3m cid: references.
---
emacs/notmuch-show.el | 45 +
1 file changed, 37 insertions(+), 8 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-s
Besides generally cleaning up the code and separating the general
content ID handling from the w3m-specific code, this fixes several
problems.
Foremost is that, previously, the code roughly assumed that referenced
parts would be in the same multipart/related as the reference.
According to RFC 2392
Previously this did its own caching, but this is now supported by more
generally by `notmuch-get-bodypart-binary'.
---
emacs/notmuch-show.el | 23 ---
1 file changed, 8 insertions(+), 15 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index f29428a..11e
(The actual code change here is small, but requires re-indenting
existing code.)
---
emacs/notmuch-lib.el | 64
1 file changed, 40 insertions(+), 24 deletions(-)
diff --git a/emacs/notmuch-lib.el b/emacs/notmuch-lib.el
index 3154725..f8e5165 10
Unibyte strings are meant for representing binary data. In practice,
using unibyte versus multibyte strings affects *almost* nothing. It
does happen to matter if we use the binary data in an image descriptor
(which is, helpfully, not documented anywhere and getting it wrong
results in opaque erro
`notmuch-get-bodypart-content' could do two very different things,
depending on conditions: for text/* parts other than text/html, it
would return the part content as a multibyte Lisp string *after*
charset conversion, while for other parts (including text/html), it
would return binary part content
The new function, `notmuch-get-bodypart-binary', replaces
`notmuch-get-bodypart-internal'. Whereas the old function was really
meant for internal use in `notmuch-get-bodypart-content', it was used
in a few other places. Since the difference between
`notmuch-get-bodypart-content' and `notmuch-get-
This will simplify later changes.
---
emacs/notmuch-show.el | 33 ++---
1 file changed, 10 insertions(+), 23 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index 87b4881..df2389e 100644
--- a/emacs/notmuch-show.el
+++ b/emacs/notmuch-show.el
@@
This is v2 of id:1398105468-14317-1-git-send-email-amdragon at mit.edu.
This improves some comments/documentation, fixes a bug that caused
cryptographic processing to not happen on HTML parts, and addresses
some byte compiler warnings on Emacs 23. This version has also been
rebased against the sev
Unibyte strings are meant for representing binary data. In practice,
using unibyte versus multibyte strings affects *almost* nothing. It
does happen to matter if we use the binary data in an image descriptor
(which is, helpfully, not documented anywhere and getting it wrong
results in opaque erro
`notmuch-get-bodypart-content' could do two very different things,
depending on conditions: for text/* parts other than text/html, it
would return the part content as a multibyte Lisp string *after*
charset conversion, while for other parts (including text/html), it
would return binary part content
The new function, `notmuch-get-bodypart-binary', replaces
`notmuch-get-bodypart-internal'. Whereas the old function was really
meant for internal use in `notmuch-get-bodypart-content', it was used
in a few other places. Since the difference between
`notmuch-get-bodypart-content' and `notmuch-get-
shr has really nice support for inline image rendering, but previously
we only had the hooks for w3m cid: references.
---
emacs/notmuch-show.el | 45 +
1 file changed, 37 insertions(+), 8 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-s
(The actual code change here is small, but requires re-indenting
existing code.)
---
emacs/notmuch-lib.el | 64
1 file changed, 40 insertions(+), 24 deletions(-)
diff --git a/emacs/notmuch-lib.el b/emacs/notmuch-lib.el
index 3154725..f8e5165 10
This is v2 of id:1398105468-14317-1-git-send-email-amdra...@mit.edu.
This improves some comments/documentation, fixes a bug that caused
cryptographic processing to not happen on HTML parts, and addresses
some byte compiler warnings on Emacs 23. This version has also been
rebased against the severa
Previously this did its own caching, but this is now supported by more
generally by `notmuch-get-bodypart-binary'.
---
emacs/notmuch-show.el | 23 ---
1 file changed, 8 insertions(+), 15 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index f29428a..11e
This will simplify later changes.
---
emacs/notmuch-show.el | 33 ++---
1 file changed, 10 insertions(+), 23 deletions(-)
diff --git a/emacs/notmuch-show.el b/emacs/notmuch-show.el
index 87b4881..df2389e 100644
--- a/emacs/notmuch-show.el
+++ b/emacs/notmuch-show.el
@@
On Fri, 25 Apr 2014, Mark Walters wrote:
> On Thu, 24 Apr 2014, Austin Clements wrote:
>> Quoth Mark Walters on Apr 24 at 11:46 am:
>>>
>>> On Mon, 21 Apr 2014, Austin Clements wrote:
>>> > (The actual code change here is small, but re
own to be
> defined: libxml-parse-html-region, shr-insert-document
>
> Finally, I have not really tested it as I mainly use emacs23
>
> Best wishes
>
> Mark
>
>
>
>
> On Mon, 21 Apr 2014, Austin Clements wrote:
>> I set out to quickly add support for c
On Thu, 01 May 2014, David Edmondson wrote:
> On Mon, Apr 21 2014, Austin Clements wrote:
>> +(defun notmuch-show--insert-part-text/html-shr (msg part)
>> + ;; Make sure shr is loaded before we start let-binding its globals
>> + (require 'shr)
>> + (let ((dom (
On Fri, 11 Jul 2014, David Bremner wrote:
> Austin Clements writes:
>
>> +This returns the content of the given part as a multibyte Lisp
>
> What does "multibyte" mean here? utf8? current encoding?
Elisp has two kinds of stings: "unibyte strings" and "
On Thu, 10 Jul 2014, David Bremner wrote:
> Austin Clements writes:
>
>> This will simplify later changes.
>
> I'd have preferred the whitespace changes as a seperate patch, but OK.
Not sure which whitespace changes you're referring to. Everything in
this diff is actual (minor) code changes.
On Fri, 25 Apr 2014, Mark Walters wrote:
> On Thu, 24 Apr 2014, Austin Clements wrote:
>> Quoth Mark Walters on Apr 24 at 11:46 am:
>>>
>>> On Mon, 21 Apr 2014, Austin Clements wrote:
>>> > (The actual code change here is small, but re
own to be
> defined: libxml-parse-html-region, shr-insert-document
>
> Finally, I have not really tested it as I mainly use emacs23
>
> Best wishes
>
> Mark
>
>
>
>
> On Mon, 21 Apr 2014, Austin Clements wrote:
>> I set out to quickly add support for c
On Thu, 01 May 2014, David Edmondson wrote:
> On Mon, Apr 21 2014, Austin Clements wrote:
>> +(defun notmuch-show--insert-part-text/html-shr (msg part)
>> + ;; Make sure shr is loaded before we start let-binding its globals
>> + (require 'shr)
>> + (let ((dom (
On Fri, 11 Jul 2014, David Bremner wrote:
> Austin Clements writes:
>
>> +This returns the content of the given part as a multibyte Lisp
>
> What does "multibyte" mean here? utf8? current encoding?
Elisp has two kinds of stings: "unibyte strings" and "
On Thu, 10 Jul 2014, David Bremner wrote:
> Austin Clements writes:
>
>> This will simplify later changes.
>
> I'd have preferred the whitespace changes as a seperate patch, but OK.
Not sure which whitespace changes you're referring to. Everything in
this diff is
Quoth Daniel Kahn Gillmor on Jan 21 at 4:36 pm:
> On Wed 2015-01-21 16:14:07 -0500, Austin Clements wrote:
> > I have a fix for this on shr buried deep in an old patch series that I
> > never got back to: id:1398105468-14317-12-git-send-email-amdragon at mit.edu
> >
> >
I have a fix for this on shr buried deep in an old patch series that I
never got back to: id:1398105468-14317-12-git-send-email-amdragon at mit.edu
For shr, the key is to set shr-blocked-images to ".". However, IIRC,
in the current notmuch message rendering pipeline, mm overrides this
variable wi
Quoth Daniel Kahn Gillmor on Jan 21 at 4:36 pm:
> On Wed 2015-01-21 16:14:07 -0500, Austin Clements wrote:
> > I have a fix for this on shr buried deep in an old patch series that I
> > never got back to: id:1398105468-14317-12-git-send-email-amdra...@mit.edu
> >
> >
I have a fix for this on shr buried deep in an old patch series that I
never got back to: id:1398105468-14317-12-git-send-email-amdra...@mit.edu
For shr, the key is to set shr-blocked-images to ".". However, IIRC,
in the current notmuch message rendering pipeline, mm overrides this
variable with
Quoth David Bremner on Jan 15 at 10:08 pm:
> Austin Clements writes:
>
> > From: Austin Clements
> >
> > XXX Includes reference to notmuch search --db-revision, which doesn't
> > exist.
>
> What would --db-revision do if it was implimented? Did you want
Quoth David Bremner on Jan 15 at 10:08 pm:
> Austin Clements writes:
>
> > From: Austin Clements
> >
> > XXX Includes reference to notmuch search --db-revision, which doesn't
> > exist.
>
> What would --db-revision do if it was implimented? Did you want
Just one nit. Otherwise this patch LGTM.
On January 15, 2015 12:20:08 PM EST, Jani Nikula wrote:
>
>Austin, would you mind having a look at this one please?
>
>Thanks,
>Jani.
>
>On Wed, 14 Jan 2015, Todd wrote:
>> ---
>> lib/database-private.h | 15 ---
>> lib/database.cc| 1
Just one nit. Otherwise this patch LGTM.
On January 15, 2015 12:20:08 PM EST, Jani Nikula wrote:
>
>Austin, would you mind having a look at this one please?
>
>Thanks,
>Jani.
>
>On Wed, 14 Jan 2015, Todd wrote:
>> ---
>> lib/database-private.h | 15 ---
>> lib/database.cc| 1
Hi David.
In general, "-" will negate a query term. However, Xapian's query
syntax (to which notmuch is beholden) ignores "-" at the beginning of
a query (and immediately after an open paren). Hence, if you want to
negate the first term in a query, you'll have to use "not" instead.
Hope that he
Hi David.
In general, "-" will negate a query term. However, Xapian's query
syntax (to which notmuch is beholden) ignores "-" at the beginning of
a query (and immediately after an open paren). Hence, if you want to
negate the first term in a query, you'll have to use "not" instead.
Hope that he
---
NEWS | 30 ++
1 file changed, 30 insertions(+)
diff --git a/NEWS b/NEWS
index b30ed1b..7a121e4 100644
--- a/NEWS
+++ b/NEWS
@@ -36,9 +36,39 @@ Improved `q` binding in notmuch buffers
Library changes
---
+Introduced database version 3 with support for
---
NEWS | 30 ++
1 file changed, 30 insertions(+)
diff --git a/NEWS b/NEWS
index b30ed1b..7a121e4 100644
--- a/NEWS
+++ b/NEWS
@@ -36,9 +36,39 @@ Improved `q` binding in notmuch buffers
Library changes
---
+Introduced database version 3 with support fo
These macros help clarify basic bit-twiddling code and are written to
be robust against C undefined behavior of shift operators.
---
lib/message.cc| 6 +++---
lib/notmuch-private.h | 11 +++
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/lib/message.cc b/lib/messa
Quoth Mark Walters on Oct 24 at 10:23 am:
>
> Hi
>
> I definitely like the idea: some comments below.
Agreed.
> On Fri, 24 Oct 2014, David Edmondson wrote:
> > In addition to the :authors attribute of each search result, include
> > :authors_matched and :authors_non_matched attributes. Both at
These macros help clarify basic bit-twiddling code and are written to
be robust against C undefined behavior of shift operators.
---
lib/message.cc| 6 +++---
lib/notmuch-private.h | 11 +++
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/lib/message.cc b/lib/messa
Quoth Mark Walters on Oct 24 at 10:23 am:
>
> Hi
>
> I definitely like the idea: some comments below.
Agreed.
> On Fri, 24 Oct 2014, David Edmondson wrote:
> > In addition to the :authors attribute of each search result, include
> > :authors_matched and :authors_non_matched attributes. Both at
From: Austin Clements
Previously, it was necessary to link new messages to children to work
around some (though not all) problems with the old metadata-based
approach to stored thread IDs. With ghost messages, this is no longer
necessary, so don't bother with child linking when ghost mes
---
test/T530-upgrade.sh | 21 +
1 file changed, 21 insertions(+)
diff --git a/test/T530-upgrade.sh b/test/T530-upgrade.sh
index c4c4ac8..6b42a69 100755
--- a/test/T530-upgrade.sh
+++ b/test/T530-upgrade.sh
@@ -116,4 +116,25 @@ MAIL_DIR/bar/new/21:2,
MAIL_DIR/bar/new/22:2,
M
From: Austin Clements
This fixes the broken thread order test.
---
lib/database-private.h| 2 +-
test/T260-thread-order.sh | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/database-private.h b/lib/database-private.h
index e2e4bc8..15e03cc 100644
--- a/lib/database
From: Austin Clements
Somehow this is the first upgrade pass that actually does *any* error
checking, so this also adds the bit of necessary infrastructure to
handle that.
---
lib/database.cc | 66 +++--
1 file changed, 64 insertions(+), 2
From: Austin Clements
This updates the thread linking code to use ghost messages instead of
user metadata to link messages into threads.
In contrast with the old approach, this is actually correct.
Previously, thread merging updated only the thread IDs of message
documents, not thread IDs
From: Austin Clements
This updates the message abstraction to support ghost messages: it
adds a message flag that distinguishes regular messages from ghost
messages, and an internal function for initializing a newly created
(blank) message as a ghost message.
---
lib/message.cc| 52
These macros help clarify basic bit-twiddling code and are written to
be robust against C undefined behavior of shift operators.
---
lib/message.cc| 6 +++---
lib/notmuch-private.h | 11 +++
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/lib/message.cc b/lib/messa
From: Austin Clements
This describes the structure of ghost mail documents. Ghost messages
are not yet implemented.
---
lib/database.cc | 20 ++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/lib/database.cc b/lib/database.cc
index 8fd7fad..c641bcd 100644
From: Austin Clements
This will be implemented over the next several patches. The feature
is not yet "enabled" (this does not add it to
NOTMUCH_FEATURES_CURRENT).
---
lib/database-private.h | 7 +++
lib/database.cc| 2 ++
2 files changed, 9 insertions(+)
diff --git a/li
This is v3 of
id:1412637438-4821-1-git-send-email-aclements at csail.mit.edu.
This fixes some comments, as suggested by Mark. There are no
code changes relative to v2. The diff from v2 is below.
diff --git a/lib/database.cc b/lib/database.cc
index 6e51a72..3601f9d 100644
--- a/lib/database.cc
++
From: Austin Clements
Previously, it was necessary to link new messages to children to work
around some (though not all) problems with the old metadata-based
approach to stored thread IDs. With ghost messages, this is no longer
necessary, so don't bother with child linking when ghost mes
From: Austin Clements
This fixes the broken thread order test.
---
lib/database-private.h| 2 +-
test/T260-thread-order.sh | 1 -
2 files changed, 1 insertion(+), 2 deletions(-)
diff --git a/lib/database-private.h b/lib/database-private.h
index e2e4bc8..15e03cc 100644
--- a/lib/database
From: Austin Clements
This updates the thread linking code to use ghost messages instead of
user metadata to link messages into threads.
In contrast with the old approach, this is actually correct.
Previously, thread merging updated only the thread IDs of message
documents, not thread IDs
From: Austin Clements
This updates the message abstraction to support ghost messages: it
adds a message flag that distinguishes regular messages from ghost
messages, and an internal function for initializing a newly created
(blank) message as a ghost message.
---
lib/message.cc| 52
---
test/T530-upgrade.sh | 21 +
1 file changed, 21 insertions(+)
diff --git a/test/T530-upgrade.sh b/test/T530-upgrade.sh
index c4c4ac8..6b42a69 100755
--- a/test/T530-upgrade.sh
+++ b/test/T530-upgrade.sh
@@ -116,4 +116,25 @@ MAIL_DIR/bar/new/21:2,
MAIL_DIR/bar/new/22:2,
M
From: Austin Clements
Somehow this is the first upgrade pass that actually does *any* error
checking, so this also adds the bit of necessary infrastructure to
handle that.
---
lib/database.cc | 66 +++--
1 file changed, 64 insertions(+), 2
From: Austin Clements
This describes the structure of ghost mail documents. Ghost messages
are not yet implemented.
---
lib/database.cc | 20 ++--
1 file changed, 18 insertions(+), 2 deletions(-)
diff --git a/lib/database.cc b/lib/database.cc
index 8fd7fad..c641bcd 100644
From: Austin Clements
This will be implemented over the next several patches. The feature
is not yet "enabled" (this does not add it to
NOTMUCH_FEATURES_CURRENT).
---
lib/database-private.h | 7 +++
lib/database.cc| 2 ++
2 files changed, 9 insertions(+)
diff --git a/li
These macros help clarify basic bit-twiddling code and are written to
be robust against C undefined behavior of shift operators.
---
lib/message.cc| 6 +++---
lib/notmuch-private.h | 11 +++
2 files changed, 14 insertions(+), 3 deletions(-)
diff --git a/lib/message.cc b/lib/messa
This is v3 of
id:1412637438-4821-1-git-send-email-acleme...@csail.mit.edu.
This fixes some comments, as suggested by Mark. There are no
code changes relative to v2. The diff from v2 is below.
diff --git a/lib/database.cc b/lib/database.cc
index 6e51a72..3601f9d 100644
--- a/lib/database.cc
+++ b
Quoth Mark Walters on Oct 22 at 12:17 am:
> On Tue, 07 Oct 2014, Austin Clements wrote:
> > From: Austin Clements
> >
> > Previously, it was necessary to link new messages to children to work
> > around some (though not all) problems with the old metadata-based
> &
Quoth Mark Walters on Oct 22 at 12:10 am:
> On Tue, 07 Oct 2014, Austin Clements wrote:
> > From: Austin Clements
> >
> > This updates the thread linking code to use ghost messages instead of
> > user metadata to link messages into threads.
> >
> > In
Quoth Mark Walters on Oct 22 at 12:05 am:
>
> Hi
>
> I am slowly working my way through this series: only two trivial queries
> so far.
>
> On Tue, 07 Oct 2014, Austin Clements wrote:
> > From: Austin Clements
> >
> > This updates the message ab
Quoth Mark Walters on Oct 22 at 12:17 am:
> On Tue, 07 Oct 2014, Austin Clements wrote:
> > From: Austin Clements
> >
> > Previously, it was necessary to link new messages to children to work
> > around some (though not all) problems with the old metadata-based
> &
1 - 100 of 3780 matches
Mail list logo
