Date: Sun, 20 Jul 2014 16:11:57 -0700
From: "W. Trevor King" <wking@tremily.us>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH v3] nmbug: Translate to Python
Message-ID: <20140720231157.GT8744@odin>
References:
 <84447a0ed48412e1587761d560d18cb5affd4f66.1405897133.git.wking@tremily.us>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
	protocol="application/pgp-signature"; boundary="1Dvf9Qz7hFaodvwE"
Content-Disposition: inline
In-Reply-To:
 <84447a0ed48412e1587761d560d18cb5affd4f66.1405897133.git.wking@tremily.us>
OpenPGP: id=39A2F3FA2AB17E5D8764F388FC29BDCDF15F5BE8;
	url=http://tremily.us/pubkey.txt
User-Agent: Mutt/1.5.23 (2014-03-12)
Cc: David Bremner <bremner@debian.org>
Precedence: list


--1Dvf9Qz7hFaodvwE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Sun, Jul 20, 2014 at 03:59:49PM -0700, W. Trevor King wrote:
> Most of the user-facing interface is the same, but there are a few
> changes, where reproducing the original interface was too difficult
> or I saw a change to make the underlying Git UI accessible:

It's not listed in the commit message, but another change is that
'nmbug commit' now only uses a single argument for the optional
commit-message text.  I'll document this in the v4 commit message,
after v3 has cooked for a bit.  I wanted to expose more of the
underlying 'git commit' UI, since I personally like to write my commit
messages in an editor with the notes added by 'git commit -v' to jog
my memory.  Unfortunately, we're using 'git commit-tree' instead of
'git commit', and commit-tree is too low-level for editor-launching.
I'd be interested in rewriting commit() to use 'git commit', but that
seemed like it was outside the scope of this rewrite.  So I'm not
supporting all of Git's commit syntax in this patch, but I can at
least match 'git commit -m MESSAGE' in requiring command-line commit
messages to be a single argument.

Cheers,
Trevor

--=20
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy

--1Dvf9Qz7hFaodvwE
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBAgAGBQJTzEy8AAoJEG8/JgBt8ol8qzgQAMngWzNtNFVGKzY8GBvjTsv5
Dqf/Q/9+U39mx3sLCuKcWXPJnDgklNB9Vy6duJy8jSySZ8F/CLXVVtoI59P7dgNS
DAOLC4abMmi5b7PRdqKJxRoldJo0Xui8i3S4zOBYQBctMj9JRoqNlA/fhGQJLvUR
wYFseg0by/oMwyne1WtoOPVf2QWPeX7/iYwr9R31xlkIn45DC1aF7EXF2qE88Etc
npRQC3zmuUMuIqRqHZjnKM5LML24YszTeKl/1sznoblDc6F9BmqoqP/DhB12k3mX
ghJmzNpPeHcZe0uR6J2ozolTxwX1HAXeVcg20JTcjNznb1btjT737d2GFml04Li0
wlEmjl+Uk3NwesaLyBl0J+YO2kFb5G3qHbNCdYMSR2/16r1R7CDs/EsP1pxaTzxw
kd/NsdlEYxKA2MYD1hnX1RYrp2IppDjE598Vdb545dkVqIS/asIRFlH/1BA/UUEb
V1K48/rS8ou6r5/w4LmiXeaNCNIncXRZQIokABEHg8RJdNNvcwUdjMM0Bzagwv73
gvsoysFBG+0iOYaTwklThmuO46WisVxOjBSSZ2adauFPMR9fGk++xs/nQpp+wg0d
81cJX7t9yg2644XPfu6juECysodrN127yPbeL9/iNYPqI/5GU4lDvVW09wcTbWMW
OLJTIBNj5IYyQMV6Gaht
=rn2I
-----END PGP SIGNATURE-----

--1Dvf9Qz7hFaodvwE--