public inbox for gdb@sourceware.org
 help / color / mirror / Atom feed
From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Paul_Koning@Dell.com, gdb@sourceware.org
Subject: Re: Using Py_SetPythonHome
Date: Wed, 03 Oct 2012 19:03:00 -0000	[thread overview]
Message-ID: <20121003190310.GA16945@host2.jankratochvil.net> (raw)
In-Reply-To: <83sj9v8k22.fsf@gnu.org>

On Wed, 03 Oct 2012 20:52:37 +0200, Eli Zaretskii wrote:
> > The right solution would sure be if I could just 'git pull' an update to the
> > assignments database/files.
> 
> Who or what prevents you from setting up a git repo on fencepost, or
> asking savannah admins to add copyright.list to their repo, or ...?

 * The GIT repo would have to be used read/write by all its users.
 * GIT may not be welcome at gnu.org so I would have to learn some GNU
   equivalent of GIT.
 * Life is too short to fix every little itch, interactive SSH works somehow.

As a summary from my point of view the relocations do not make sense, I also
I understand you have reasons to keep them, I have already removed these hacks
in Fedora where they IMO do not make sense.  There only still AFAIK remains
a disagreement in what should be the default './configure; make' GDB behavior.
Maybe the current state of all deployments (except non-Fedora GNU/Linux) is OK.


Thanks,
Jan

  reply	other threads:[~2012-10-03 19:03 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 [this message]
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
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=20121003190310.GA16945@host2.jankratochvil.net \
    --to=jan.kratochvil@redhat.com \
    --cc=Paul_Koning@Dell.com \
    --cc=eliz@gnu.org \
    --cc=gdb@sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).