From: "W. Trevor King" <wking@tremily.us>
To: gentoo-catalyst@lists.gentoo.org
Cc: "W. Trevor King" <wking@tremily.us>
Subject: [gentoo-catalyst] [PATCH] examples/README: Add a pointer to the releng Git repository
Date: Thu, 31 Jan 2013 17:33:56 -0500 [thread overview]
Message-ID: <2aba0c00b43da9b80f1dd079d156c49db1f5ca03.1359671283.git.wking@tremily.us> (raw)
In-Reply-To: <510AD8A1.4030901@gmail.com>
From: "W. Trevor King" <wking@tremily.us>
Thanks to Dustin C. Hatch for pointing this out, because I wasn't able
to find it on my own. Having a pointer distributed with Catalyst
should help other newcomers find example spec files written by folks
who know what they're doing ;). The current examples lack a full
stage1-through-stage3 progression.
---
On Thu, Jan 31, 2013 at 02:48:33PM -0600, Dustin C. Hatch wrote:
> http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=tree;f=releases/weekly/specs
Wonderful, thanks. This patch adds the pointers to Catalyst, so other
folks can find them without emailing the list for assistance ;).
examples/README | 5 +++++
1 file changed, 5 insertions(+)
create mode 100644 examples/README
diff --git a/examples/README b/examples/README
new file mode 100644
index 0000000..bfd517a
--- /dev/null
+++ b/examples/README
@@ -0,0 +1,5 @@
+For further examples, see the releases/weekly/specs directory [1] in
+the releng Git repository [2].
+
+[1]: http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=tree;f=releases/weekly/specs;hb=HEAD
+[2]: http://git.overlays.gentoo.org/gitweb/?p=proj/releng.git;a=summary
--
1.8.1.336.g94702dd
next prev parent reply other threads:[~2013-01-31 22:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 20:27 [gentoo-catalyst] Newer releng spec files? W. Trevor King
2013-01-31 20:48 ` Dustin C. Hatch
2013-01-31 22:33 ` W. Trevor King [this message]
2013-03-02 20:22 ` [gentoo-catalyst] Bumping a few patches (releng-link, bugs, spec-comments, howto) W. Trevor King
2013-04-10 15:09 ` [gentoo-catalyst] " W. Trevor King
2013-05-03 17:25 ` [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, ...) W. Trevor King
2013-12-14 4:58 ` [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, howto) W. Trevor King
2013-12-20 5:02 ` [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, howto-stage-descriptions, ...) W. Trevor King
2013-12-31 17:03 ` W. Trevor King
2014-01-01 6:20 ` Jorge Manuel B. S. Vicetto
2014-01-01 17:54 ` W. Trevor King
2014-01-06 3:55 ` [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, term-env-var, ...) W. Trevor King
2014-06-14 16:14 ` [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, pandoc-mediawiki, ...) W. Trevor King
2014-06-14 23:27 ` Brian Dolbec
2014-06-15 0:04 ` W. Trevor King
2014-06-15 1:01 ` Brian Dolbec
2013-01-31 22:56 ` [gentoo-catalyst] Newer releng spec files? W. Trevor King
-- strict thread matches above, loose matches on Subject: below --
2013-02-01 2:19 [gentoo-catalyst] [PATCH] examples: Add newlines to accidentally unwrapped comment lines W. Trevor King
2013-02-01 1:34 ` [gentoo-catalyst] [PATCH] Move bug-reporting and mailing list notes from TODO to README W. Trevor King
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=2aba0c00b43da9b80f1dd079d156c49db1f5ca03.1359671283.git.wking@tremily.us \
--to=wking@tremily.us \
--cc=gentoo-catalyst@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