From: Jameson Graef Rollins <jrollins@finestructure.net>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [RFC PATCH] bikeshed uncrustify options
Date: Wed, 25 Jan 2012 10:31:03 -0800 [thread overview]
Message-ID: <87y5sv63dk.fsf@servo.finestructure.net> (raw)
In-Reply-To: <871uqn7i0l.fsf@servo.finestructure.net>
[-- Attachment #1: Type: text/plain, Size: 1058 bytes --]
On Wed, 25 Jan 2012 10:29:30 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> On Wed, 25 Jan 2012 20:24:19 +0200, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> > On Wed, 25 Jan 2012 08:41:52 -0800, Jameson Graef Rollins <jrollins@finestructure.net> wrote:
> > > On Wed, 25 Jan 2012 17:21:26 +0200, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> > > > -type GMimeObject mime_node_t
> > > > +type GMimeObject GMimeCryptoContext GMimeCipherContext
> > > > +type mime_node_t notmuch_message_t
> > >
> > > This must be a mistake. Presumably this hasn't been properly rebased
> > > against the latest master, which includes Austin's part 2 show rewrite.
> >
> > $ git reset --hard origin/master
> > $ git describe
> > debian/0.11-1-116-ge6e10b8
> > $ git am foo.am
> > Applying: bikeshed uncrustify options
> > $
>
> Ok, but obviously this patch should not be making this change.
hrm, actually I just noticing the file that this diff applies to. Maybe
that's what you want? I don't understand this uncrustify stuff.
jamie.
[-- Attachment #2: Type: application/pgp-signature, Size: 835 bytes --]
prev parent reply other threads:[~2012-01-25 18:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-25 15:21 [RFC PATCH] bikeshed uncrustify options Tomi Ollila
2012-01-25 15:48 ` Jani Nikula
2012-01-25 16:41 ` Jameson Graef Rollins
2012-01-25 18:24 ` Tomi Ollila
2012-01-25 18:29 ` Jameson Graef Rollins
2012-01-25 18:31 ` Jameson Graef Rollins [this message]
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=87y5sv63dk.fsf@servo.finestructure.net \
--to=jrollins@finestructure.net \
--cc=notmuch@notmuchmail.org \
--cc=tomi.ollila@iki.fi \
/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).