From: ams@gnu.org (Alfred M. Szmidt)
To: Jan Kratochvil <jan.kratochvil@redhat.com>
Cc: eliz@gnu.org, Paul_Koning@Dell.com, gdb@sourceware.org
Subject: Re: Using Py_SetPythonHome
Date: Wed, 03 Oct 2012 20:11:00 -0000 [thread overview]
Message-ID: <E1TJVI7-0000yf-Go@fencepost.gnu.org> (raw)
In-Reply-To: <20121003184340.GB16194@host2.jankratochvil.net> (message from Jan Kratochvil on Wed, 3 Oct 2012 20:43:40 +0200)
> > > There do not exist any multi-user systems anymore. Each
> > > developer has her own virtual machine (in fact many of them),
> > > therefore sure with root access and with proper normal
> > > automatic package management there.
> >
> > That is not true.
>
> Of course, it isn't. Example: fencepost.gnu.org.
I hope you do not mean this seriously. I understand there still
exist some such systems but they are a relict needing to be
replaced. And at least from the systems around me (not just Red
Hat) they already have been replaced.
I work at a place where we have 100+ multi-user systems per machine
(and hundreds of machines) that have no plans on being replaced, more
like extended and expanded; we recently finished a migration from i386
boxen to x86_64 boxen, switching OS (to RHEL from SuSE) and other
stuff.
Relocation is a dream of anyone who futzes with special deliviers for
weirdo platforms; even plain old GNU/Linux boxen.
The right solution would sure be if I could just 'git pull' an
update to the assignments database/files.
Setting up a simple cronjob to copy copyright into a vcs repo that you
pull from fp is quite trivial. I have a small Makefile that copies
copyright.list (amongst other things) to my latop, and commits it to
VCS. If you want, I can bundle up that script for you.
Cheers!
next prev parent reply other threads:[~2012-10-03 20:11 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-12 23:23 Meador Inge
2012-09-17 17:07 ` Joel Brobecker
2012-09-17 17:46 ` Jan Kratochvil
2012-09-18 19:38 ` Doug Evans
2012-09-19 8:04 ` Jan Kratochvil
2012-09-21 15:37 ` Joel Brobecker
2012-09-21 15:44 ` Jan Kratochvil
2012-09-21 15:58 ` Joel Brobecker
2012-09-21 17:28 ` Jan Kratochvil
2012-10-02 13:09 ` Joel Brobecker
2012-10-03 15:13 ` Jan Kratochvil
2012-10-03 15:14 ` Jan Kratochvil
2012-10-03 15:39 ` Joel Brobecker
2012-10-03 17:44 ` Eli Zaretskii
2012-10-03 17:54 ` Jan Kratochvil
2012-10-03 17:57 ` Paul_Koning
2012-10-03 18:35 ` Eli Zaretskii
2012-10-03 18:43 ` Jan Kratochvil
2012-10-03 18:52 ` Eli Zaretskii
2012-10-03 19:03 ` Jan Kratochvil
2012-10-03 19:10 ` Eli Zaretskii
2012-10-03 19:54 ` Paul_Koning
2012-10-03 20:04 ` Jan Kratochvil
2012-10-03 20:11 ` Alfred M. Szmidt [this message]
2012-10-03 18:40 ` Eli Zaretskii
2012-10-03 19:26 ` Terekhov, Mikhail
2012-10-04 7:33 ` John Gilmore
2012-10-11 8:42 ` Jan Kratochvil
2012-10-11 14:54 ` Doug Evans
2012-09-21 15:55 ` Meador Inge
2012-09-21 16:01 ` Jan Kratochvil
2012-09-21 16:36 ` Doug Evans
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=E1TJVI7-0000yf-Go@fencepost.gnu.org \
--to=ams@gnu.org \
--cc=Paul_Koning@Dell.com \
--cc=eliz@gnu.org \
--cc=gdb@sourceware.org \
--cc=jan.kratochvil@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).