From: Michael <barra_cuda@katamail.com>
To: git@vger.kernel.org
Cc: Junio C Hamano <junkio@cox.net>
Subject: Re: [PATCH] Documentation: add KMail in SubmittingPatches
Date: Tue, 6 Feb 2007 14:45:07 +0100 [thread overview]
Message-ID: <200702061445.07657.barra_cuda@katamail.com> (raw)
In-Reply-To: <7vveigkmpv.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano:
> Michael <barra_cuda@katamail.com> writes:
> > @@ -331,3 +330,21 @@ whitespaces (fatal in patches). Running 'C-u g' to
> > display the
> > message in raw form before using '|' to run the pipe can work
> > this problem around.
[...]
> This is quite interesting -- notice your own hunk header @@ ... @@ line?
I see. It's this account's fault: now I know because I've tried with
another account. I didn't know it had this glitch, sorry.
> I do not use KMail myself, so I cannot comment on the procedure,
> but from the cursory look it *should* do the right thing. Only
> that it makes me a bit nervous to see your hunk header being
> line wrapped.
>
> Doubly interesting is that somebody appears to have added two
> message IDs.
>
> Subject: [PATCH] Documentation: add KMail in SubmittingPatches
> Date: Mon, 5 Feb 2007 14:27:32 +0100
> User-Agent: KMail/1.9.4
> Message-Id: <200702051427.32532.barra_cuda@katamail.com>
> Message-ID: <20070205132150.123659@dial-up-mi-449.lombardiacom.it>
This is my current account's fault too. So I used KMail correctly,
but my mail server did something to the message. I guess I should
use another account. Anyway, if some other KMail user has something
to say about this issue, it will make things clearer.
Bye.
next prev parent reply other threads:[~2007-02-06 13:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-03 6:40 Why is it bad to rewind a branch that has already been pushed out? Junio C Hamano
2007-02-03 10:40 ` Andy Parkins
2007-02-03 19:42 ` Junio C Hamano
2007-02-04 18:01 ` Andy Parkins
2007-02-03 13:20 ` Theodore Tso
2007-02-04 16:16 ` Robin Rosenberg
2007-02-04 20:08 ` Junio C Hamano
[not found] ` <20070205132150.123659@dial-up-mi-449.lombardiacom.it>
2007-02-05 13:27 ` [PATCH] Documentation: add KMail in SubmittingPatches Michael
2007-02-06 3:07 ` Junio C Hamano
2007-02-06 13:45 ` Michael [this message]
2007-02-06 14:16 ` Jakub Narebski
2007-02-06 14:47 ` Andy Parkins
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=200702061445.07657.barra_cuda@katamail.com \
--to=barra_cuda@katamail.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).