public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: app-doc/gnucash-docs/
Date: Tue,  6 Dec 2022 12:33:15 +0000 (UTC)	[thread overview]
Message-ID: <1670329556.7b1c57494b767668fbed02f818e1f1327cb933ca.sam@gentoo> (raw)

commit:     7b1c57494b767668fbed02f818e1f1327cb933ca
Author:     Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Dec  6 12:25:56 2022 +0000
Commit:     Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Dec  6 12:25:56 2022 +0000
URL:        https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7b1c5749

app-doc/gnucash-docs: add sourceforge upstream metadata

github is just a mirror, so it's useful to have, but sourceforge
is still an official upstream location.

Fixes: cc5376cf0d9e57ee59a157a8b066a2e56edfadc8
Signed-off-by: Sam James <sam <AT> gentoo.org>

 app-doc/gnucash-docs/metadata.xml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/app-doc/gnucash-docs/metadata.xml b/app-doc/gnucash-docs/metadata.xml
index e26f0babcb44..0c83fc97a657 100644
--- a/app-doc/gnucash-docs/metadata.xml
+++ b/app-doc/gnucash-docs/metadata.xml
@@ -6,6 +6,7 @@
 		<name>Aaron W. Swenson</name>
 	</maintainer>
 	<upstream>
+		<remote-id type="sourceforge">gnucash</remote-id>
 		<remote-id type="github">Gnucash/gnucash</remote-id>
 	</upstream>
 </pkgmetadata>


             reply	other threads:[~2022-12-06 12:33 UTC|newest]

Thread overview: 69+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-06 12:33 Sam James [this message]
  -- strict thread matches above, loose matches on Subject: below --
2024-12-26  2:54 [gentoo-commits] repo/gentoo:master commit in: app-doc/gnucash-docs/ Sam James
2024-12-26  2:54 Sam James
2024-07-20  4:38 Sam James
2024-05-28 18:19 Arthur Zamarin
2024-05-28 17:01 Sam James
2024-05-11 18:36 Aaron W. Swenson
2024-01-20 14:42 Aaron W. Swenson
2023-09-23 21:07 Aaron W. Swenson
2023-05-12 23:58 Sam James
2023-05-03 23:05 Sam James
2023-05-03 18:54 Arthur Zamarin
2023-01-04 21:00 Andreas Sturmlechner
2023-01-04  6:31 Arthur Zamarin
2023-01-04  6:17 Arthur Zamarin
2022-12-06 12:47 Sam James
2022-12-06 12:33 Sam James
2022-12-06 12:02 Sam James
2022-12-06 12:02 Sam James
2022-12-06 12:02 Sam James
2022-05-07  5:00 Sam James
2022-03-30 14:14 Yixun Lan
2021-12-09  6:39 Sam James
2021-12-08 23:00 Sam James
2021-11-18 14:38 Aaron W. Swenson
2021-05-05  9:47 Aaron W. Swenson
2021-03-09 18:54 Aaron W. Swenson
2021-03-08 10:26 Sam James
2021-03-08 10:25 Sam James
2020-12-30 11:38 Aaron W. Swenson
2020-12-30 11:38 Aaron W. Swenson
2020-11-20 20:10 Aaron W. Swenson
2020-11-11 18:51 Sam James
2020-09-28  1:40 Aaron W. Swenson
2020-08-29 13:21 Sam James
2020-07-27  3:01 Aaron W. Swenson
2020-07-21 12:09 Aaron W. Swenson
2020-05-21 11:14 Aaron W. Swenson
2020-05-12  6:31 Agostino Sarubbo
2020-03-28 21:46 Aaron W. Swenson
2019-11-27  8:16 Agostino Sarubbo
2019-11-26 12:52 Agostino Sarubbo
2019-10-13 12:14 Mart Raudsepp
2019-10-13 11:40 Andreas Sturmlechner
2019-08-30 17:50 Michał Górny
2019-07-18 12:56 Aaron W. Swenson
2019-07-03  9:37 Aaron W. Swenson
2019-04-10 11:30 Aaron W. Swenson
2019-01-09 13:06 Aaron W. Swenson
2018-11-10 12:03 Mikle Kolyada
2018-10-07 10:19 Aaron Swenson
2018-10-06 21:52 Mikle Kolyada
2018-10-05  4:10 Thomas Deutschmann
2018-10-03  2:03 Aaron Swenson
2018-08-11 11:25 Aaron Swenson
2018-08-11 11:23 Aaron Swenson
2018-07-09  9:18 Aaron Swenson
2018-05-13 16:03 Aaron Swenson
2018-05-13 16:03 Aaron Swenson
2018-04-27 20:24 Aaron Swenson
2018-01-06 17:03 Aaron Swenson
2017-02-15 16:49 Mart Raudsepp
2017-01-10 20:14 Pacho Ramos
2017-01-10 20:14 Pacho Ramos
2016-01-30 12:23 Pacho Ramos
2016-01-30 12:23 Pacho Ramos
2015-10-17 11:53 Pacho Ramos
2015-10-17 11:53 Pacho Ramos
2015-09-05 17:57 Pacho Ramos

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=1670329556.7b1c57494b767668fbed02f818e1f1327cb933ca.sam@gentoo \
    --to=sam@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