public inbox for gentoo-catalyst@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Jorge Manuel B. S. Vicetto" <jmbsvicetto@gentoo.org>
To: gentoo-catalyst@lists.gentoo.org
Subject: Re: [gentoo-catalyst] Re: Bumping a few patches (releng-link, bugs, spec-comments, howto-stage-descriptions, ...)
Date: Wed, 1 Jan 2014 06:20:21 +0000 (UTC)	[thread overview]
Message-ID: <alpine.LNX.2.00.1401010609290.11502@woodpecker.gentoo.org> (raw)
In-Reply-To: <20131231170308.GE29195@odin.tremily.us>

On Tue, 31 Dec 2013, W. Trevor King wrote:

> It's been another two weeks, and I've added another patch, so here's
> another summary of my outstanding patches:
>
>  branch: sshd-tweak
>  summary: livecdfs-update.sh: Fix '/etc/sshd' check for sshd_config tweaks
>  http://mid.gmane.org/a0100e7d5c8905c99230cac46b963718d3826f5a.1362315628.git.wking@tremily.us

The change seems fine. We'll have to look more carefully to see if we 
should drop the if entirely.

>  branch: xsession
>  summary: livecdfs-update.sh: Set XSESSION in /etc/env.d/90xsession
>  summary: livecdfs-update.sh: Run env-update to pick up any /etc/env.d/ changes
>  http://mid.gmane.org/e523136669974c6586b2c6d28b3f50684a7a7bb7.1362252114.git.wking@tremily.us
>  http://mid.gmane.org/20130302221014.GA31585@odin.tremily.us

TO be honest, I don't care about livecd. The change seems ok, so I'm ok 
with applying it. Zero might care about this stuff.

>  branch: releng-link
>  summary: examples/README: Add a pointer to the releng Git repository
>  http://mid.gmane.org/2aba0c00b43da9b80f1dd079d156c49db1f5ca03.1359671283.git.wking@tremily.us

Looks good and make sense.

>  branch: bugs
>  summary: Move bug-reporting and mailing list notes from TODO to README
>  http://mid.gmane.org/f226aa91ea25a61d07ee9721d47d3ef5143fa7d2.1359682421.git.wking@tremily.us

+1

>  branch: spec-comments
>  summary: examples: Add newlines to accidentally unwrapped comment lines
>  http://mid.gmane.org/80e0140be0a82ad25a6c775386e5778566b7ec5c.1359685121.git.wking@tremily.us

+1 We really need to review and update the examples, though.

>  branch: pkgcache-warning
>  summary: doc/catalyst-config.5.txt: Document linking issues with binary packages
>  http://mid.gmane.org/cover.1366075786.git.wking@tremily.us

Missing diff? I couldn't open the links as well.

>  branch: cleanup-subarch-xml
>  summary: Makefile: Cleanup doc/subarches.generated.xml
>  http://mid.gmane.org/091a6955b8a95308adf58cb6ef3d0ba1e05fc08c.1387169465.git.wking@tremily.us

I didn't check the generated files, but this seems ok.

>  branch: howto-stage-descriptions
>  summary: doc/HOWTO.txt: Fix stage descriptions
>  http://mid.gmane.org/3614940041744d107ceff3e460e8549204c9b498.1387512969.git.wking@tremily.us

I already replied to this one in the ml.

>  branch: term-env-var
>  summary: modules/generic_target.py: Pass TERM through to the chroot environment
>  http://mid.gmane.org/739db1331359acd82717c3eed4bced3828ad7e8d.1388285607.git.wking@tremily.us
>
> term-env-var is new this week.  The others have been around for a
> while.  All branches are also available in my public repository [1].

I'm fine with this change. dol-sen already talked with me about adding it 
to the 2.X branch as well.

> Cheers,
> Trevor
>
> [1]: http://git.tremily.us/?p=catalyst.git
>     git://tremily.us/catalyst.git

Cheers and thanks for your work and patience with us.
Regards,

Jorge.


  reply	other threads:[~2014-01-01  6:20 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 [this message]
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=alpine.LNX.2.00.1401010609290.11502@woodpecker.gentoo.org \
    --to=jmbsvicetto@gentoo.org \
    --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