Subject: Re: Displaying tags with many messages very slow in Emacs
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
From: bnt <webservice@bontempi.net>
In-Reply-To: <87bosx9fxr.fsf@gilead.invalid>
Date: Tue, 1 Nov 2011 14:36:27 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <109E7309-AA04-4252-B4ED-23B94A7AB2D8@bontempi.net>
References: <B676D1F6-04DD-49A9-8284-5CF17D6C4602@bontempi.net>
	<87fwi99vlj.fsf@wyzanski.jamesvasile.com>
	<72587727-5371-4BFF-A21C-ECA11D2F7BB5@bontempi.net>
	<87bosx9fxr.fsf@gilead.invalid>
To: Daniel Schoepe <daniel@schoepe.org>
Cc: notmuch@notmuchmail.org
Precedence: list


On 2011, Oct 31, at 19:25 , Daniel Schoepe wrote:

> On Mon, 31 Oct 2011 16:43:22 +0100, bnt <webservice@bontempi.net> =
wrote:
>> I am not too proficient with the patch utility. Is there some kind of
>> scheduled git commits timeline?
>=20
> Unfortunately, there's a huge number of outstanding patches at the
> moment, so it's impossible to say when/if it will be applied.
>=20
>> If not, I guess it will be a good time to learn patching.
>=20
> There's no need to use the patch binary directly when the patches are
> sent in a format git understands, which is generally the case here. To
> apply patches from a thread, you can use `git am patches.mbox' where
> patches.mbox contains the mails with the patches.
>=20
> If you're using the emacs UI for notmuch, you can open only those
> messages with the patches you want in a thread and pipe them to an =
mbox
> file like this:
>=20
> C-u | cat > ~/patches.mbox
>=20
> If there are no conflicts due to more recent changes to the =
repository,
> git am patches.mbox will apply them using the commit messages from the
> mails.
>=20
> FWIW: There's another more recent series of patches that accomplishes =
a
> similar goal: id:"cover.1319833617.git.jani@nikula.org"
>=20
> Cheers,
> Daniel


Thank you so much for the explanation, and thanks to Jani for those =
patches.

I will work my way into applying them.

As just a plain user, I was wondering if it would be possible to have a =
"dev" or "untested" branch in the git repo, where one could just get all =
the latest patches?=20

Of course it would not be desirable if it would just complicate the =
developers life.

Thank you so much once again,

Sam=