From: Eric Wong <e@80x24.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Santiago Torres <santiago@nyu.edu>,
meta@public-inbox.org, git@vger.kernel.org, peff@peff.net,
sunshine@sunshineco.com, walters@verbum.org,
Lukas Puehringer <luk.puehringer@gmail.com>
Subject: Re: [PATCH v6 4/6] builtin/tag: add --format argument for tag -v
Date: Wed, 18 Jan 2017 20:16:44 +0000 [thread overview]
Message-ID: <20170118201644.GA13758@starla> (raw)
In-Reply-To: <xmqq4m0wb43w.fsf@gitster.mtv.corp.google.com>
Junio C Hamano <gitster@pobox.com> wrote:
> Santiago Torres <santiago@nyu.edu> writes:
>
> <<nothing>>???
>
> Eric, I've noticed that this message
>
> http://public-inbox.org/git/20170118182831.pkhqu2np3bh2puei@LykOS.localdomain/
>
> and all messages from Santiago appear empty when they come via
> public-inbox.org; the reason I suspect we haven't heard much
> complaints is because nobody else around here sends multipart/signed
> disposition inline other than Santiago.
Eeep! This looks like a regression I introduced when working
around Richard Hansen's S/MIME mails the other week on git@vger:
https://public-inbox.org/meta/20170110222235.GB27356@dcvr/T/#u
Worse is they now corrupted on the way in into the git repo
because of search indexing. Will fix ASAP. Thanks for the
heads up.
next prev parent reply other threads:[~2017-01-18 20:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170117233723.23897-1-santiago@nyu.edu>
[not found] ` <20170117233723.23897-5-santiago@nyu.edu>
[not found] ` <xmqqmvepb4oj.fsf@gitster.mtv.corp.google.com>
[not found] ` <xmqqh94wb4y0.fsf@gitster.mtv.corp.google.com>
[not found] ` <20170118182831.pkhqu2np3bh2puei@LykOS.localdomain>
2017-01-18 18:44 ` [PATCH v6 4/6] builtin/tag: add --format argument for tag -v Junio C Hamano
2017-01-18 18:50 ` Santiago Torres
2017-01-18 20:16 ` Eric Wong [this message]
2017-01-19 0:37 ` Eric Wong
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://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170118201644.GA13758@starla \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=luk.puehringer@gmail.com \
--cc=meta@public-inbox.org \
--cc=peff@peff.net \
--cc=santiago@nyu.edu \
--cc=sunshine@sunshineco.com \
--cc=walters@verbum.org \
/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://80x24.org/public-inbox.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).