<feed xmlns='http://www.w3.org/2005/Atom'>
<title>notmuch/devel, branch 0.26_rc0</title>
<subtitle>thread-based email index, search, and tagging</subtitle>
<id>https://git.notmuchmail.org/git/notmuch/atom?h=0.26_rc0</id>
<link rel='self' href='https://git.notmuchmail.org/git/notmuch/atom?h=0.26_rc0'/>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/'/>
<updated>2017-12-16T12:20:13Z</updated>
<entry>
<title>nmbug: Only error for invalid diff lines in tags/</title>
<updated>2017-12-16T12:20:13Z</updated>
<author>
<name>W. Trevor King</name>
<email>wking@tremily.us</email>
</author>
<published>2017-10-16T18:01:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=572259885af4d5858c3be5c2119ec7019e1ca617'/>
<id>urn:sha1:572259885af4d5858c3be5c2119ec7019e1ca617</id>
<content type='text'>
Avoid:

  Traceback (most recent call last):
    File "/home/nmbug/bin/nmbug", line 834, in &lt;module&gt;
      args.func(**kwargs)
    File "/home/nmbug/bin/nmbug", line 385, in checkout
      status = get_status()
    File "/home/nmbug/bin/nmbug", line 580, in get_status
      maybe_deleted = _diff_index(index=index, filter='D')
    File "/home/nmbug/bin/nmbug", line 658, in _diff_index
      for id, tag in _unpack_diff_lines(stream=p.stdout):
    File "/home/nmbug/bin/nmbug", line 678, in _unpack_diff_lines
      'Invalid line in diff: {!r}'.format(line.strip()))
  ValueError: Invalid line in diff: u'.mailmap'

With this commit, folks can commit READMEs, .mailmap, etc. to their
nmbug repositories, and 'nmbug diff' and 'status' won't choke on them.
If you want to check for this sort of thing, you can set --log-level
to info or greater.  nmbug will still error if the unrecognized path
is under tags/, since that's more likely to be a user error.
</content>
</entry>
<entry>
<title>nmbug: Auto-checkout in clone if it wouldn't clobber</title>
<updated>2017-12-11T13:07:09Z</updated>
<author>
<name>W. Trevor King</name>
<email>wking@tremily.us</email>
</author>
<published>2017-10-10T22:49:51Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=7ef3b65376b87829441736f04b3231021f561d84'/>
<id>urn:sha1:7ef3b65376b87829441736f04b3231021f561d84</id>
<content type='text'>
We currently auto-checkout after pull and merge to make those more
convenient.  They're guarded against data-loss with a leading
_insist_committed().  This commit adds the same convenience to clone,
since in most cases users will have no NMBPREFIX-prefixed tags in
their database when they clone.  Users that *do* have
NMBPREFIX-prefixed tags will get a warning (and I've bumped the
default log level to warning so folks who don't set --log-level will
see it) like:

  $ nmbug clone http://nmbug.notmuchmail.org/git/nmbug-tags.git
  Cloning into '/tmp/nmbug-clone.g9dvd0tv'...
  Checking connectivity: 16674, done.
  Branch config set up to track remote branch config from origin.
  Not checking out to avoid clobbering existing tags: notmuch::0.25, ...
</content>
</entry>
<entry>
<title>nmbug: Accept failures to unset core.worktree in clone</title>
<updated>2017-12-11T13:06:47Z</updated>
<author>
<name>W. Trevor King</name>
<email>wking@tremily.us</email>
</author>
<published>2017-10-10T22:49:50Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=0a1558471f70ec8591c9d40808d1ffd930742054'/>
<id>urn:sha1:0a1558471f70ec8591c9d40808d1ffd930742054</id>
<content type='text'>
Since 6311cfaf (init: do not set unnecessary core.worktree,
2016-09-25, 2.11.0 [1]), Git has no longer set core.worktree when
--separate-git-dir is used.  This broke clone with:

  $ nmbug clone http://nmbug.notmuchmail.org/git/nmbug-tags.git
  Cloning into '/tmp/nmbug-clone.33gg442e'...
  Checking connectivity: 16674, done.
  ['git', '--git-dir', '/home/wking/.nmbug', 'config', '--unset', 'core.worktree'] exited with 5
  $ echo $?
  1

The initial discussion that lead to the Git change is in [2], and
there is some more discussion around this specific change in [3].
There is some useful background on working trees in this 2009 message
[4].  There is also a git-worktree(1) since df0b6cfb (worktree: new
place for "git prune --worktrees", 2015-06-29, 2.5.0 [5]) which grew
the ability to add new worktrees in 799767cc (Merge branch
'es/worktree-add', 2015-07-13, 2.5.0 [6]).  Folks relying on
core.worktree in the --separate-git-dir case fall into the "former
case" in [4], and as Junio pointed out in that message, Git
operations like 'add' don't really work there.

In nmbug we don't want core.worktree, because our effective working
tree is the notmuch database.  By accepting failed core.worktree
unsets, clone will work with Gits older and younger than 2.11.0.

[1]: https://github.com/git/git/commit/6311cfaf93716bcc43dd1151cb1763e3f80d8099
[2]: https://public-inbox.org/git/CALqjkKZO_y0DNcRJjooyZ7Eso7yBMGhvZ6fE92oO4Su7JeCeng@mail.gmail.com/
[3]: https://public-inbox.org/git/87h94d8cwi.fsf@kyleam.com/
[4]: https://public-inbox.org/git/7viqbsw2vn.fsf@alter.siamese.dyndns.org/
[5]: https://github.com/git/git/commit/df0b6cfbda88144714541664fb501146d6465a82
[6]: https://github.com/git/git/commit/799767cc98b2f8e6f82d0de4bef9b5e8fcc16e97

Reported-by: Daniel Kahn Gillmor &lt;dkg@fifthhorseman.net&gt;
</content>
</entry>
<entry>
<title>nmbug: Respect 'expect' in _spawn(..., wait=True)</title>
<updated>2017-12-11T13:06:30Z</updated>
<author>
<name>W. Trevor King</name>
<email>wking@tremily.us</email>
</author>
<published>2017-10-10T22:49:49Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=e263c5b1f9e21d049ab04be0bec3ec7dc5bbc30e'/>
<id>urn:sha1:e263c5b1f9e21d049ab04be0bec3ec7dc5bbc30e</id>
<content type='text'>
Fixing a bug from 7f2cb3be (nmbug: Translate to Python, 2014-10-03).
The bug had no direct impact though, because none of the wait=True
callers were setting expect.

Also add expected codes to the debug messages, to help log readers
understand why nonzero exits are occasionally accepted.
</content>
</entry>
<entry>
<title>devel/check-out-of-tree-build.sh: consistent naming, consistent quoting</title>
<updated>2017-10-05T10:40:36Z</updated>
<author>
<name>Tomi Ollila</name>
<email>tomi.ollila@iki.fi</email>
</author>
<published>2017-10-03T05:18:25Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=54aef071590cb23f61da943daa29080cf7446696'/>
<id>urn:sha1:54aef071590cb23f61da943daa29080cf7446696</id>
<content type='text'>
Renamed from out-of-tree-build-check.sh to be consistent with
other files in this directory.

Fixed quoting in "$srcdir" usage for additional robustness, other
quoting changes for consistency.
</content>
</entry>
<entry>
<title>devel: add script to test out-of-tree builds</title>
<updated>2017-10-02T10:25:06Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-09-11T17:17:47Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=379de73603d98da6a9cc95a9af914f98bd393e95'/>
<id>urn:sha1:379de73603d98da6a9cc95a9af914f98bd393e95</id>
<content type='text'>
Something I used for 'git bisect run', but we should really add this
as part of our process.
</content>
</entry>
<entry>
<title>Use rooted paths in .gitignore files</title>
<updated>2017-08-18T22:42:35Z</updated>
<author>
<name>Vladimir Panteleev</name>
<email>notmuch@thecybershadow.net</email>
</author>
<published>2017-08-17T00:41:10Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ca4688e103c644fa383108a79668e8e0b4dbe262'/>
<id>urn:sha1:ca4688e103c644fa383108a79668e8e0b4dbe262</id>
<content type='text'>
A leading / in paths in a .gitignore file matches the beginning of the
path, meaning that for patterns without slashes, git will match files
only in the current directory as opposed to in any subdirectory.

Prefix relevant paths with / in .gitignore files, to prevent
accidentally ignoring files in subdirectories and possibly slightly
improve the performance of "git status".
</content>
</entry>
<entry>
<title>devel/schemata: describe version 4</title>
<updated>2017-07-04T11:32:37Z</updated>
<author>
<name>David Bremner</name>
<email>david@tethera.net</email>
</author>
<published>2017-06-03T17:47:33Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=9eacd7d367aff4c5e8069e4b9f4c7ed8f466f6ee'/>
<id>urn:sha1:9eacd7d367aff4c5e8069e4b9f4c7ed8f466f6ee</id>
<content type='text'>
Replace numeric errors with human readable flags.  Not all sig_error
keys will necessarily be generated with a given version of gmime.

Drop status "none" as it's currrently unused and I don't know what
it's for.
</content>
</entry>
<entry>
<title>cli/show: add content-disposition to structured output message parts</title>
<updated>2017-02-28T12:03:00Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-02-26T18:33:48Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=ea20a932f1b8bc849db5ed35c1f355990f186146'/>
<id>urn:sha1:ea20a932f1b8bc849db5ed35c1f355990f186146</id>
<content type='text'>
Help the clients decide how to display parts.

Test updates by Mark Walters &lt;markwalters1009@gmail.com&gt;.
One more test fix by db
</content>
</entry>
<entry>
<title>cli/show: list all filenames of a message in the formatted output</title>
<updated>2017-02-26T11:41:33Z</updated>
<author>
<name>Jani Nikula</name>
<email>jani@nikula.org</email>
</author>
<published>2017-02-25T13:31:31Z</published>
<link rel='alternate' type='text/html' href='https://git.notmuchmail.org/git/notmuch/commit/?id=14c60cf168ac3b0f277188c16e6012b7ebdadde7'/>
<id>urn:sha1:14c60cf168ac3b0f277188c16e6012b7ebdadde7</id>
<content type='text'>
Instead of just having the first filename for the message, list all
duplicate filenames of the message as a list in the formatted
outputs. This bumps the format version to 3.
</content>
</entry>
</feed>
