From: bdowning@lavos.net (Brian Downing)
To: Aidan Van Dyk <aidan@highrise.ca>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Lars Magne Ingebrigtsen <larsi+gmane@gnus.org>
Subject: Re: Applying patches from gmane can be dangerous.
Date: Thu, 7 Feb 2008 09:03:06 -0600 [thread overview]
Message-ID: <20080207150306.GU26392@lavos.net> (raw)
In-Reply-To: <20080207145036.GM26016@yugib.highrise.ca>
On Thu, Feb 07, 2008 at 09:50:36AM -0500, Aidan Van Dyk wrote:
> If you look at the message Junio referenced, it hit gmane first from the
> msysgit list (@google), not the git list (@vger). So when the git@vger
> mail came in with the same message-id, it simply linked it to the
> already stored message
>
> Basically, we have to convince groups that are commonly "overlapping"
> git@vger on gmane not to choose hiding the emails. In this case, the
> msysgit group.
Thanks, that clears things up for me.
-bcd
next prev parent reply other threads:[~2008-02-07 15:04 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
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 [this message]
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=20080207150306.GU26392@lavos.net \
--to=bdowning@lavos.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=aidan@highrise.ca \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=larsi+gmane@gnus.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.