From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org, patrick@gentoo.org
Subject: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild
Date: Sun, 08 Nov 2009 17:21:18 +0300 [thread overview]
Message-ID: <1257690078.8341.1384.camel@tablet> (raw)
In-Reply-To: <E1N76Ny-0004jL-Q2@stork.gentoo.org>
В Вск, 08/11/2009 в 11:56 +0000, Patrick Lauer (patrick) пишет:
> patrick 09/11/08 11:56:46
> Log:
> Bump
> file : http://sources.gentoo.org/viewcvs.py/gentoo-x86/app-forensics/foremost/foremost-1.5.6.ebuild?rev=1.1&view=markup
> Index: foremost-1.5.6.ebuild
> ===================================================================
> inherit eutils toolchain-funcs
>
> DESCRIPTION="A console program to recover files based on their headers and footers"
> HOMEPAGE="http://foremost.sourceforge.net/"
> #SRC_URI="mirror://sourceforge/${PN}/${P}.tar.gz"
> # starting to hate sf.net ...
> SRC_URI="http://foremost.sourceforge.net/pkg/foremost-1.5.6.tar.gz"
Patrick, do you remember the answer on question number 1 in end-quiz?
> KEYWORDS="~ppc ~x86 ~amd64"
> src_install() {
> dobin foremost
This question did not existed in end-quiz at times you were mentored,
but still you are supposed to follow gentoo development and you are
supposed to know the answers on quizzes. Please check question 15 of
end-quiz.
--
Peter.
next parent reply other threads:[~2009-11-08 14:22 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1N76Ny-0004jL-Q2@stork.gentoo.org>
2009-11-08 14:21 ` Peter Volkov [this message]
2009-11-08 14:50 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild Patrick Lauer
2009-11-08 14:56 ` Petteri Räty
2009-11-08 15:06 ` Patrick Lauer
2009-11-08 15:12 ` Fabian Groffen
2009-11-08 15:20 ` Petteri Räty
2009-11-08 15:29 ` Mike Frysinger
2009-11-08 15:30 ` Mike Auty
2009-11-08 17:37 ` Peter Volkov
2009-11-08 18:10 ` Patrick Lauer
2009-11-08 18:24 ` Mike Frysinger
2009-11-08 19:08 ` Patrick Lauer
2009-11-08 19:27 ` Mark Loeser
2009-11-08 19:54 ` Patrick Lauer
2009-11-08 22:22 ` Mike Frysinger
2009-11-08 20:09 ` Ben de Groot
2009-11-08 20:15 ` Mark Loeser
2009-11-08 20:22 ` Ben de Groot
2009-11-08 22:19 ` Mike Frysinger
2009-11-09 12:36 ` Maciej Mrozowski
2009-11-09 20:10 ` Mike Frysinger
2009-11-09 0:37 ` Vlastimil Babka
2009-11-09 12:08 ` [gentoo-dev] QA is unimportant? (was: gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild) Peter Volkov
2009-11-09 12:32 ` Ben de Groot
2009-11-09 16:10 ` [gentoo-dev] QA is unimportant? Richard Freeman
2009-11-09 23:50 ` Thilo Bangert
2009-11-09 16:30 ` Patrick Lauer
2009-11-09 20:16 ` Mike Frysinger
2009-11-09 21:36 ` Robert Bradbury
2009-11-09 22:52 ` Patrick Lauer
2009-11-09 23:45 ` Mike Frysinger
2009-11-10 0:01 ` Mike Frysinger
2009-11-09 23:13 ` Samuli Suominen
2009-11-09 22:26 ` Dawid Węgliński
2009-11-10 8:07 ` Rémi Cardona
2009-11-08 19:46 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in app-forensics/foremost: ChangeLog foremost-1.5.6.ebuild Thomas Sachau
2009-11-08 22:16 ` Mike Frysinger
2009-11-08 23:36 ` Richard Freeman
2009-11-09 23:57 ` Mike Frysinger
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=1257690078.8341.1384.camel@tablet \
--to=pva@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=patrick@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