From: Jari Aalto <jari.aalto@cante.net>
To: git@vger.kernel.org
Subject: Re: Applying patches from gmane can be dangerous.
Date: Thu, 07 Feb 2008 10:01:32 +0200 [thread overview]
Message-ID: <ve51w5yb.fsf@blue.sea.net> (raw)
In-Reply-To: 7vodatqu6w.fsf@gitster.siamese.dyndns.org
* Wed 2008-02-06 Junio C Hamano <gitster@pobox.com>
* Message-Id: 7vodatqu6w.fsf@gitster.siamese.dyndns.org
> I picked up the qsort patch from Brian while reading the list
> via gmane's newsfeed and applied it without realizing that it
> was one of the articles whose addresses on all the address
> header fields _and_ all strings that look like e-mail addresses
> have been mangled by gmane. Sign-offs by Dscho and Steffen
FYI,
Emacs Gnus + news.gmane.org gives access to raw articles with single
command. Suppose cursor is at thread start "!"
! R. [ 40: Junio C Hamano ] Applying patches from gmane can be dangerous.
R. [ 19: Nicolas Pitre ]
Pressing "C-u g" will display the unmodified article as seen by mail
transport. Running git's apply command can be automated pretty easily
from there.
Jari
--
Welcome to FOSS revolution: we fix and modify until it shines
next prev parent reply other threads:[~2008-02-07 8:02 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-05 21:10 [PATCH v2] compat: Add simplified merge sort implementation from glibc Brian Downing
[not found] ` <20080205211044.GP26392-oU/tDdhfGLReoWH0uzbU5w@public.gmane.org>
2008-02-05 22:21 ` Johannes Schindelin
[not found] ` <alpine.LSU.1.00.0802052220500.8543-OGWIkrnhIhzN0uC3ymp8PA@public.gmane.org>
2008-02-06 2:47 ` Brian Downing
2008-02-07 4:14 ` Applying patches from gmane can be dangerous Junio C Hamano
2008-02-07 4:29 ` Nicolas Pitre
2008-02-07 9:08 ` Junio C Hamano
2008-02-10 10:51 ` 'next' will be rewound and rebuilt after feature releases Junio C Hamano
2008-02-07 8:01 ` Jari Aalto [this message]
2008-02-07 8:21 ` Applying patches from gmane can be dangerous Junio C Hamano
2008-02-07 9:05 ` Mike Hommey
2008-02-07 12:42 ` Johannes Schindelin
2008-02-07 13:32 ` Brian Downing
2008-02-07 14:50 ` Aidan Van Dyk
2008-02-07 15:03 ` Brian Downing
2008-02-07 16:10 ` Johannes Schindelin
2008-02-11 21:16 ` Johannes Schindelin
2008-02-07 14:10 ` Frank Lichtenheld
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=ve51w5yb.fsf@blue.sea.net \
--to=jari.aalto@cante.net \
--cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.