git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Junio C Hamano <gitster@pobox.com>
Cc: Filip Navara <filip.navara@gmail.com>,
	git@vger.kernel.org, tortoisegit-dev@googlegroups.com
Subject: Re: git-mailsplit and TortoiseGit bugs
Date: Tue, 23 Jun 2009 00:42:58 -0400	[thread overview]
Message-ID: <20090623044258.GA26875@coredump.intra.peff.net> (raw)
In-Reply-To: <7vskhra7el.fsf@alter.siamese.dyndns.org>

On Mon, Jun 22, 2009 at 09:41:38PM -0700, Junio C Hamano wrote:

> Jeff King <peff@peff.net> writes:
> 
> > mailinfo: accept useless non-multipart boundary attributes
> 
> Is this "accept"? Or do you mean "ignore"?

Saying "ignore" is probably more accurate.

-Peff

      reply	other threads:[~2009-06-23  4:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-22 17:53 git-mailsplit and TortoiseGit bugs Filip Navara
2009-06-22 20:29 ` Jeff King
2009-06-22 21:46   ` Filip Navara
2009-06-23  1:26     ` Frank Li
2009-06-23  8:13       ` Filip Navara
2009-06-23  4:41   ` Junio C Hamano
2009-06-23  4:42     ` Jeff King [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=20090623044258.GA26875@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=filip.navara@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=tortoisegit-dev@googlegroups.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).