From: "Ulrich Müller" <ulm@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/
Date: Tue, 30 Mar 2021 16:10:07 +0000 (UTC) [thread overview]
Message-ID: <1617120054.be07d60d328e03200d4864be66782123aad756f1.ulm@gentoo> (raw)
commit: be07d60d328e03200d4864be66782123aad756f1
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Mar 21 04:36:51 2021 +0000
Commit: Ulrich Müller <ulm <AT> gentoo <DOT> org>
CommitDate: Tue Mar 30 16:00:54 2021 +0000
URL: https://gitweb.gentoo.org/proj/devmanual.git/commit/?id=be07d60d
ebuild-maintenance/new-ebuild: mention pkgdev as an alternative to repoman
Signed-off-by: Sam James <sam <AT> gentoo.org>
Signed-off-by: Ulrich Müller <ulm <AT> gentoo.org>
ebuild-maintenance/new-ebuild/text.xml | 7 ++++---
1 file changed, 4 insertions(+), 3 deletions(-)
diff --git a/ebuild-maintenance/new-ebuild/text.xml b/ebuild-maintenance/new-ebuild/text.xml
index ad7f74c..d8608be 100644
--- a/ebuild-maintenance/new-ebuild/text.xml
+++ b/ebuild-maintenance/new-ebuild/text.xml
@@ -48,9 +48,10 @@ examples.
</p>
<p>
-When committing to git, all developers should use <c>repoman commit</c>
-instead of <c>git commit</c> to submit their ebuilds. Before committing,
-please run <c>repoman full</c> to make sure you didn't forget something.
+When committing to git, all developers should use <c>repoman commit</c> or
+<c>pkgdev commit</c> with <c>pkgdev push</c> instead of <c>git commit</c> to
+submit their ebuilds. Before committing, please run <c>repoman full</c> or
+<c>pkgcheck scan</c> to make sure you didn't forget something.
</p>
</body>
next reply other threads:[~2021-03-30 16:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-30 16:10 Ulrich Müller [this message]
-- strict thread matches above, loose matches on Subject: below --
2023-10-21 11:46 [gentoo-commits] proj/devmanual:master commit in: ebuild-maintenance/new-ebuild/ Ulrich Müller
2022-01-22 23:40 Sam James
2021-04-07 17:35 Ulrich Müller
2020-03-02 10:49 Ulrich Müller
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=1617120054.be07d60d328e03200d4864be66782123aad756f1.ulm@gentoo \
--to=ulm@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