From: Agostino Sarubbo <ago@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Repoman check before file stable request
Date: Wed, 13 Jun 2012 19:07:32 +0200 [thread overview]
Message-ID: <10228743.sFIYRSaXJD@devil> (raw)
In-Reply-To: <20120613185840.76328c0d@epia.jer-c2.orkz.net>
[-- Attachment #1: Type: text/plain, Size: 594 bytes --]
On Wednesday 13 June 2012 18:58:40 Jeroen Roovers wrote:
> ekeyword $(ARCHES) ${EBUILD}
>
> Saves time.
Yep, good example.
> > repoman manifest
> > repoman commit -p -m "foo"
>
> Why would you commit the changes when you only intended to check
> deps before filing a stabilisation request?
-p will not commit anything. You can see only what happens if you go ahead
without -p.
Anyway, the idea is: check the other(s) ~arch depend(s) before file stable
request in any method that you prefer.
--
Agostino Sarubbo ago -at- gentoo.org
Gentoo/AMD64 Arch Security Liaison
GPG: 0x7CD2DC5D
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
prev parent reply other threads:[~2012-06-13 17:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-11 13:42 [gentoo-dev] Repoman check before file stable request Agostino Sarubbo
2012-06-11 14:36 ` Agostino Sarubbo
2012-06-13 16:58 ` Jeroen Roovers
2012-06-13 17:02 ` Jeroen Roovers
2012-06-13 17:07 ` Agostino Sarubbo [this message]
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=10228743.sFIYRSaXJD@devil \
--to=ago@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