From: Miklos Vajna <vmiklos@frugalware.org>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [patch] Import "git-forest" into contrib/
Date: Thu, 20 Mar 2008 03:16:30 +0100 [thread overview]
Message-ID: <20080320021630.GR2663@genesis.frugalware.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0803192301330.25695@fbirervta.pbzchgretzou.qr>
[-- Attachment #1: Type: text/plain, Size: 447 bytes --]
On Wed, Mar 19, 2008 at 11:23:55PM +0100, Jan Engelhardt <jengelh@computergmbh.de> wrote:
> Actually, it's `git log -1 -p` that I used. PINE traditionally
> trashes the direct mbox output of git, i.e. Message-ID is rewritten
> by PINE again when using Continue Postponed, but apparently only on
> non-PINE messages to begin with. I just recently switched to alpine,
> maybe it's better there.
or just use git-send-email if your mailer is broken.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2008-03-20 2:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-18 18:25 [patch] Import "git-forest" into contrib/ Jan Engelhardt
2008-03-19 21:11 ` Miklos Vajna
2008-03-19 21:22 ` Jan Engelhardt
2008-03-19 21:52 ` Junio C Hamano
2008-03-19 22:23 ` Jan Engelhardt
2008-03-20 2:16 ` Miklos Vajna [this message]
2008-03-19 21:21 ` Jakub Narebski
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=20080320021630.GR2663@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jengelh@computergmbh.de \
/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).