From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Doug Evans <dje@google.com>
Cc: Pedro Alves <palves@redhat.com>,
Joel Brobecker <brobecker@adacore.com>,
gdb-patches@sourceware.org
Subject: Re: [patch] Do not open Python scripts twice #2 [Re: [RFC] Crash sourcing Python script on Windows]
Date: Tue, 24 Jan 2012 19:41:00 -0000 [thread overview]
Message-ID: <20120124194044.GA2855@host2.jankratochvil.net> (raw)
In-Reply-To: <CADPb22TAY2wcQwoKpLPxHc4pNLbBCZnXXMTZtsVR+Yri8OhUrA@mail.gmail.com>
On Tue, 24 Jan 2012 19:32:18 +0100, Doug Evans wrote:
Skipped the discussion what can be more statistically useful and rather chose:
> On Tue, Jan 24, 2012 at 6:36 AM, Jan Kratochvil > <jan.kratochvil@redhat.com> wrote:
> > And it does not make sense to discuss what is better or worse, it is only
> > important the standard is to not do directories relocation.
>
> Well, the important thing is to pick what works for the right reasons,
> not introduce unwarranted incompatibilities, etc.
If you want to patch other 10000 or how many packages so they all use
directory relocations, you are free to do. I prefer to remove the directory
relocations from the single (maybe there are few of such) differing GDB
package instead.
As a next step of this discussion I can only submit a ticket to FESCo (Fedora
Engineering Steering Committee) to validate whether my Fedora
non-relocatability patch/idea is right or not.
> [AIUC] I'd instead impose requiring chroot on Fedora package testers
> than regular users.
Normal users always use only the system installed GDB. Anything else is
unsupported.
> That still doesn't help me decide whether this patch should go in (as is).
> If you wanted to punt on windows and just always impose a double
> open(), I'd be ok with that, for example.
Without MS-Windows the Joel's patch would not be invented and we would just
always do single open() like before. Or I do not understand it now.
Thanks,
Jan
next prev parent reply other threads:[~2012-01-24 19:41 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 23:24 [RFC] Crash sourcing Python script on Windows Joel Brobecker
2011-09-29 2:00 ` Paul_Koning
2011-09-29 2:19 ` John Spencer
2011-09-29 4:47 ` Joel Brobecker
2011-09-29 7:30 ` Eli Zaretskii
2011-09-29 8:54 ` Kai Tietz
2011-09-29 9:48 ` Eli Zaretskii
2011-09-29 9:51 ` Kai Tietz
2011-09-29 10:54 ` Pedro Alves
2011-09-29 12:33 ` Eli Zaretskii
2011-09-29 12:48 ` Kai Tietz
2011-09-29 13:19 ` Pedro Alves
2011-09-29 7:26 ` Eli Zaretskii
2011-10-03 20:05 ` Tom Tromey
2011-09-29 7:20 ` Eli Zaretskii
2011-10-03 20:02 ` Tom Tromey
2011-10-03 20:53 ` Joel Brobecker
2011-10-04 17:08 ` Tom Tromey
2012-01-23 18:14 ` [patch] Do not open Python scripts twice #2 [Re: [RFC] Crash sourcing Python script on Windows] Jan Kratochvil
2012-01-23 18:41 ` Pedro Alves
2012-01-23 21:55 ` Jan Kratochvil
2012-01-23 22:08 ` Doug Evans
2012-01-23 22:47 ` Jan Kratochvil
2012-01-23 23:47 ` Doug Evans
2012-01-24 14:45 ` Jan Kratochvil
2012-01-24 18:56 ` Doug Evans
2012-01-24 19:41 ` Jan Kratochvil [this message]
2012-01-24 22:20 ` Doug Evans
2012-01-24 23:49 ` Jan Kratochvil
2012-01-25 22:30 ` Jan Kratochvil
2012-01-26 7:18 ` Joel Brobecker
2012-01-26 22:03 ` [commit] " Jan Kratochvil
2012-01-24 15:15 ` Pedro Alves
2012-01-23 19:57 ` Pedro Alves
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=20120124194044.GA2855@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=brobecker@adacore.com \
--cc=dje@google.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@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