From: "W. Trevor King" <wking@tremily.us>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Newer releng spec files?
Date: Thu, 31 Jan 2013 17:56:44 -0500 [thread overview]
Message-ID: <20130131225643.GA6204@odin.tremily.us> (raw)
In-Reply-To: <510AD8A1.4030901@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 780 bytes --]
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
There's all sorts of good stuff in this repository ;). However, I
find this odd:
$ sha1sum scripts/stage_build.sh tools/stage_build.sh
b802363986a31fd929bd7fa92d5a5a98501f78ac scripts/stage_build.sh
b802363986a31fd929bd7fa92d5a5a98501f78ac tools/stage_build.sh
Is the duplication accidental? Perhaps one script should be a symlink
to the other? Perhaps tools/stage_build.sh was supposed to be removed
in commit 498f935c?
Cheers,
Trevor
--
This email may be signed or encrypted with GnuPG (http://www.gnupg.org).
For more information, see http://en.wikipedia.org/wiki/Pretty_Good_Privacy
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2013-01-31 22:56 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 ` [gentoo-catalyst] [PATCH] examples/README: Add a pointer to the releng Git repository W. Trevor King
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 ` W. Trevor King [this message]
-- 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=20130131225643.GA6204@odin.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