public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Brian Dolbec" <brian.dolbec@gmail.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/catalyst:rewrite-on-master commit in: examples/
Date: Fri, 22 Nov 2013 07:13:26 +0000 (UTC)	[thread overview]
Message-ID: <1385100109.85fdddcc5cffa3977e809e1da3527337557f30d7.dol-sen@gentoo> (raw)

commit:     85fdddcc5cffa3977e809e1da3527337557f30d7
Author:     W. Trevor King <wking <AT> tremily <DOT> us>
AuthorDate: Thu Jan 31 22:25:47 2013 +0000
Commit:     Brian Dolbec <brian.dolbec <AT> gmail <DOT> com>
CommitDate: Fri Nov 22 06:01:49 2013 +0000
URL:        http://git.overlays.gentoo.org/gitweb/?p=proj/catalyst.git;a=commit;h=85fdddcc

examples/README: Add a pointer to the releng Git repository

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.

---
 examples/README | 5 +++++
 1 file changed, 5 insertions(+)

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


             reply	other threads:[~2013-11-22  7:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-22  7:13 Brian Dolbec [this message]
  -- strict thread matches above, loose matches on Subject: below --
2013-11-22  7:13 [gentoo-commits] proj/catalyst:rewrite-on-master commit in: examples/ Brian Dolbec

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=1385100109.85fdddcc5cffa3977e809e1da3527337557f30d7.dol-sen@gentoo \
    --to=brian.dolbec@gmail.com \
    --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