From: "Jeroen Roovers (jer)" <jer@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] gentoo-x86 commit in sys-power/nvclock: nvclock-9999.ebuild Manifest
Date: Mon, 3 Jan 2011 03:50:28 +0000 (UTC) [thread overview]
Message-ID: <20110103035028.5123820057@flycatcher.gentoo.org> (raw)
jer 11/01/03 03:50:28
Modified: Manifest
Removed: nvclock-9999.ebuild
Log:
Old.
(Portage version: 2.2.0_alpha11/cvs/Linux i686)
Revision Changes Path
1.4 sys-power/nvclock/Manifest
file : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-power/nvclock/Manifest?rev=1.4&view=markup
plain: http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-power/nvclock/Manifest?rev=1.4&content-type=text/plain
diff : http://sources.gentoo.org/viewvc.cgi/gentoo-x86/sys-power/nvclock/Manifest?r1=1.3&r2=1.4
Index: Manifest
===================================================================
RCS file: /var/cvsroot/gentoo-x86/sys-power/nvclock/Manifest,v
retrieving revision 1.3
retrieving revision 1.4
diff -u -r1.3 -r1.4
--- Manifest 3 Jan 2011 03:48:37 -0000 1.3
+++ Manifest 3 Jan 2011 03:50:28 -0000 1.4
@@ -8,6 +8,5 @@
DIST nvclock0.8b4.tar.gz 336999 RMD160 02dbfde37514b34c7f0e5a8b71e8205e32575dcc SHA1 758b3848b036e2b3e25368cfec4c6cd82a963dc9 SHA256 bdb695e869822c4740c361bcace81b5527b774002d42785c986da9a92d7a9b0b
EBUILD nvclock-0.8_beta4-r4.ebuild 1667 RMD160 ffe2b7d52bcb997bd4c2d251706973f3e66741ed SHA1 5923f348d3e8273e5bad11b9fc418b019ed3e072 SHA256 c2c64e4f36ae4e2994743a93e9aaafe7508895eef3dc779e8600bbee73b70a68
EBUILD nvclock-0.8_p20110102.ebuild 1150 RMD160 f70981a0ea08a71b36c304f605d674eac8698129 SHA1 69e23f7de6e85e6ddc5370a85e05708b77596d9f SHA256 67508aa0f4c530f3fbb244d8dc9d46f19020c4992d3ad3148b5f224db6af5a45
-EBUILD nvclock-9999.ebuild 1469 RMD160 7e58dbb38cbc91d423f98f2dfbcc8c56e3e361d5 SHA1 04f7a040685f646455a2f41cdcdc01fd43dda5c1 SHA256 56bff045986375d4350fa6fb2fd7500b145783901df23da4d9d43481e8702b50
MISC ChangeLog 7614 RMD160 31dee25f308dcfba840ac6f4a7accd331ecff4e6 SHA1 1cae788f3034551d16b083ba4d0ef166c25d6c0c SHA256 b117fb861312ef837e99c95f67082371eefb3bb59c9beb6f63c5e7175372f78d
MISC metadata.xml 336 RMD160 9f23751790d0f622dc0f0c96961ea5e618542c20 SHA1 8a10d1f48537909fe3d4857f6ecf74ae35d3de17 SHA256 7045abb398fdbbf41bcfdea62eb5a8264569a8a65cf61519f0f8b8ce8ed0afe9
reply other threads:[~2011-01-03 3:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20110103035028.5123820057@flycatcher.gentoo.org \
--to=jer@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox