From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Eric Raible" <raible@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git am with MIME
Date: Thu, 21 Aug 2008 09:31:31 +0200 [thread overview]
Message-ID: <81b0412b0808210031l1caec384x8e085acafd413784@mail.gmail.com> (raw)
In-Reply-To: <loom.20080821T033231-805@post.gmane.org>
2008/8/21 Eric Raible <raible@gmail.com>:
> Alex Riesen <raa.lkml <at> gmail.com> writes:
>> (Some people'll kill me for that :)
>
> And why shouldn't they when:
>
> strbuf_remove(&f, at - f.buf, el + (at[el] != 0));
>
> is infinitely better in every possible way? ;)
Because that's just as ugly as "?:", brackets and all
prev parent reply other threads:[~2008-08-21 7:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-19 15:50 git am with MIME Lea Wiemann
2008-08-19 17:07 ` Jeff King
2008-08-20 19:57 ` Alex Riesen
2008-08-20 21:58 ` Jeff King
2008-08-21 3:34 ` Eric Raible
2008-08-21 7:31 ` Alex Riesen [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=81b0412b0808210031l1caec384x8e085acafd413784@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=raible@gmail.com \
/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.
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 NNTP newsgroup(s).