From: Mike Hommey <mh@glandium.org>
To: Junio C Hamano <gitster@pobox.com>
Cc: Jari Aalto <jari.aalto@cante.net>, git@vger.kernel.org
Subject: Re: Applying patches from gmane can be dangerous.
Date: Thu, 7 Feb 2008 10:05:01 +0100 [thread overview]
Message-ID: <20080207090500.GA2296@glandium.org> (raw)
In-Reply-To: <7vsl05p46n.fsf@gitster.siamese.dyndns.org>
On Thu, Feb 07, 2008 at 12:21:36AM -0800, Junio C Hamano <gitster@pobox.com> wrote:
> Maybe you run a much newer Gnus, and Lars taught "C-u g" to
> unmangle them. After all, gmane and Gnus are both his
> creations, so it _is_ possible. But somehow I doubt it.
If that can be unmangled, what would be the purpose of mangling in the first
place ? If the mangling is any useful, it can't be unmangled. If it can, it
should just be removed.
Mike
next prev parent reply other threads:[~2008-02-07 9:05 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 ` Applying patches from gmane can be dangerous Jari Aalto
2008-02-07 8:21 ` Junio C Hamano
2008-02-07 9:05 ` Mike Hommey [this message]
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=20080207090500.GA2296@glandium.org \
--to=mh@glandium.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jari.aalto@cante.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).