Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 542182 - Git commits are being posted twice on the gentoo-commits mailing list
Summary: Git commits are being posted twice on the gentoo-commits mailing list
Status: RESOLVED FIXED
Alias: None
Product: Gentoo Infrastructure
Classification: Unclassified
Component: Git (show other bugs)
Hardware: All Linux
: Normal normal (vote)
Assignee: Gentoo Infrastructure
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-03-04 21:46 UTC by Markos Chandras (RETIRED)
Modified: 2015-03-04 22:57 UTC (History)
0 users

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markos Chandras (RETIRED) gentoo-dev 2015-03-04 21:46:46 UTC
I noticed that git commits are listed twice in the gentoo-commits mailing list

The second commit it's not listed in the http://archives.gentoo.org/gentoo-commits/threads/2015-03/ but here are two emails with duplicate content

First one:
From: "Bernard Cafarelli" <voyageur@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Content-Transfer-Encoding: 8bit
Content-type: text/plain; charset=UTF-8
Reply-To: gentoo-dev@lists.gentoo.org, "Bernard Cafarelli" <voyageur@gentoo.org>
Message-ID: <1425481671.5568d94f2122884c9d8cedc42bf48b500884305a.voyageur@gentoo>
Subject: [gentoo-commits] proj/nx:master commit in: metadata/cache/net-misc/, net-misc/nxplayer/


Second one:

From: "git@oystercatcher mirror+tproxy" <git@oystercatcher.gentoo.org>
To: gentoo-commits@lists.gentoo.org
Content-Transfer-Encoding: 8bit
Content-type: text/plain; charset=UTF-8
Reply-To: gentoo-dev@lists.gentoo.org, "git@oystercatcher mirror+tproxy" <git@oystercatcher.gentoo.org>
Message-ID: <1425481671.5568d94f2122884c9d8cedc42bf48b500884305a.git@gentoo>
Subject: [gentoo-commits] proj/nx:master commit in: metadata/cache/net-misc/, net-misc/nxplayer/
Comment 1 Alex Legler (RETIRED) archtester gentoo-dev Security 2015-03-04 22:57:17 UTC
The commit you quoted is also the very last one before I fixed it.