public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: glibc: pt_chown setuid going away by default
Date: Wed, 17 Apr 2013 20:43:59 +0000 (UTC)	[thread overview]
Message-ID: <pan$56e39$6dd2a21c$9cc99219$ef067b09@cox.net> (raw)
In-Reply-To: CAGfcS_=wVX_25UR-MjNPZESNeO4g9t_R_9TtJs5W-suFov6fhA@mail.gmail.com

Rich Freeman posted on Wed, 17 Apr 2013 14:36:59 -0400 as excerpted:

> On Wed, Apr 17, 2013 at 2:35 PM, Mike Frysinger <vapier@gentoo.org>
> wrote:
>> it's at times like this i wish we had a git repo.  `git log -p -C -M`
>> is great at tracking this sort of stuff down.
> 
> I don't want to hijack this thread, but I don't believe we have a
> tracker for the migration of docs / website / etc to git.  Is there
> simply not interest?  I'm not sure what complexities exist compared to
> the portage migration.

I'd guess that would be upto the docs team, etc.  And while they might 
conceivably be interested, it's evidently not a priority or (as 
individual projects lack the complicating issues of the tree in general) 
they'd probably have it done by now, just as the various other projects 
already running git-based overlays or whatever.

The main tree is the big one, tho.  With many projects already running 
git internally, once the tree switches over, it's probably pretty safe to 
assume everything else (possibly with an occasional exception) will as 
well.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman



  reply	other threads:[~2013-04-17 20:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-10  5:15 [gentoo-dev] glibc: pt_chown setuid going away by default Mike Frysinger
2013-04-10 16:26 ` "Paweł Hajdan, Jr."
2013-04-10 18:56 ` Rich Freeman
2013-04-10 19:32   ` Mike Frysinger
2013-04-11  2:27     ` [gentoo-dev] " Duncan
2013-04-11 15:43     ` [gentoo-dev] " James Cloos
2013-04-11 16:49       ` Mike Frysinger
2013-04-12  2:19         ` [gentoo-dev] " Duncan
2013-04-12 20:05           ` Mike Frysinger
2013-04-12 19:41         ` [gentoo-dev] " James Cloos
2013-04-12 20:08           ` Mike Frysinger
2013-04-13 17:06             ` Jeroen Roovers
2013-04-14 23:02               ` James Cloos
2013-04-17 18:35               ` Mike Frysinger
2013-04-17 18:36                 ` Rich Freeman
2013-04-17 20:43                   ` Duncan [this message]
2013-04-20  6:55                 ` Sergei Trofimovich
2013-04-12  6:50 ` Maxim Kammerer
2013-04-12 16:22   ` Mike Frysinger
2013-04-12 17:20     ` Maxim Kammerer
2013-04-12 18:54       ` Mike Gilbert
2013-04-12 19:56       ` Mike Frysinger

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='pan$56e39$6dd2a21c$9cc99219$ef067b09@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --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