public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Marco Leise" <marco.leise@gmx.de>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/user/dlang:master commit in: /
Date: Mon,  9 May 2022 23:16:26 +0000 (UTC)	[thread overview]
Message-ID: <1652138156.14dbb69d0fe9d9ae3dba747ac8400399f0b4cac1.mleise@gentoo> (raw)

commit:     14dbb69d0fe9d9ae3dba747ac8400399f0b4cac1
Author:     Marco Leise <marco.leise <AT> gmx <DOT> de>
AuthorDate: Mon May  9 23:15:56 2022 +0000
Commit:     Marco Leise <marco.leise <AT> gmx <DOT> de>
CommitDate: Mon May  9 23:15:56 2022 +0000
URL:        https://gitweb.gentoo.org/repo/user/dlang.git/commit/?id=14dbb69d

Added note about --signoff to the README.md

Signed-off-by: Marco Leise <marco.leise <AT> gmx.de>

 README.md | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/README.md b/README.md
index 557398c..1a6a6d1 100644
--- a/README.md
+++ b/README.md
@@ -77,6 +77,9 @@ Import files from libraries are placed in `/usr/include/dlang/<library>/` matchi
 
 ## Contributing
 If you want to maintain a package or generally help update the repository or have a suggestion, just drop me a [note](mailto:marco.leise@gmx.de). If things move too slowly, I can add you to the team with commit rights. That's better than maintaining your own fork and having people search for updates in multiple places. Should this repository appear abandoned at some point and no one can be reached, please contact the [Gentoo GitHub org](https://github.com/gentoo) that has ownership of it.
+
+For pull requests please add `--signoff` to your commits. Otherwise they cannot be pushed to Gentoo's Git repository.
+
 ### When adding new compiler versions
 At first there is not much to be done, but once the first arch is stable, it should be added as a compiler option for Dlang packages, by providing a description for its USE-flag in `profile/use.desc` and tying it into `eclass/dlang-compilers.eclass`. This way it knows which compiler release is based on which version of the D language specification, which is crucial for dependency management.
 ### When changing paths in compiler ebuilds


             reply	other threads:[~2022-05-09 23:17 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-09 23:16 Marco Leise [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-03-08 19:09 [gentoo-commits] repo/user/dlang:master commit in: / Horodniceanu Andrei
2023-12-17 13:37 Marco Leise
2023-09-28  4:56 Marco Leise
2023-08-16  5:03 Marco Leise
2023-07-22 11:55 Marco Leise
2023-07-22 11:46 Marco Leise
2022-10-13 16:03 Marco Leise
2022-07-25 11:15 Marco Leise
2022-07-23 12:24 Marco Leise
2022-07-15  4:37 Marco Leise
2022-07-15  4:24 Marco Leise
2022-07-15  4:24 Marco Leise
2022-05-10 12:52 Marco Leise
2022-05-10 10:04 Marco Leise
2022-05-09 23:47 Marco Leise
2022-05-09 23:22 Marco Leise
2021-01-25 17:23 Marco Leise
2020-08-15  1:50 Marco Leise
2020-05-30 16:47 Marco Leise
2020-04-06  2:42 Marco Leise
2020-03-03 14:58 Marco Leise
2019-11-30 12:01 Marco Leise

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=1652138156.14dbb69d0fe9d9ae3dba747ac8400399f0b4cac1.mleise@gentoo \
    --to=marco.leise@gmx.de \
    --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