unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Carl Worth <cworth@cworth.org>
To: Daniel Kahn Gillmor <dkg@fifthhorseman.net>,
	notmuch mailing list <notmuch@notmuchmail.org>
Subject: Re: NOTMUCH_STATUS_LAST_STATUS problematic across additive library upgrades
Date: Mon, 07 Dec 2015 15:37:33 -0800	[thread overview]
Message-ID: <87vb89n83m.fsf@wondoo.home.cworth.org> (raw)
In-Reply-To: <87y4d5q38i.fsf@alice.fifthhorseman.net>

[-- Attachment #1: Type: text/plain, Size: 624 bytes --]

On Mon, Dec 07 2015, Daniel Kahn Gillmor wrote:
> In particular, if a user builds against version X of the library, then
> version X+1 is released with a new status code (but no
> backward-incompatible API/ABI changes that would require an SONAME
> bump), then the value of NOTMUCH_STATUS_LAST_STATUS would change, but
> the application using notmuch wouldn't know about it.

Can you envision a scenario where this would actually lead to a bug?

It's meant to provide a convenience. It's clearly documented as "not an
actual status value", so, yes, no client code should ever be passing
that value into the library.

-Carl


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]

  reply	other threads:[~2015-12-07 23:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-07 22:54 NOTMUCH_STATUS_LAST_STATUS problematic across additive library upgrades Daniel Kahn Gillmor
2015-12-07 23:37 ` Carl Worth [this message]
2015-12-08  0:19   ` Daniel Kahn Gillmor
2015-12-08  5:22     ` Carl Worth
2015-12-08 15:55       ` Daniel Kahn Gillmor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://notmuchmail.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87vb89n83m.fsf@wondoo.home.cworth.org \
    --to=cworth@cworth.org \
    --cc=dkg@fifthhorseman.net \
    --cc=notmuch@notmuchmail.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://yhetil.org/notmuch.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).