Mirror of the gdb mailing list
 help / color / mirror / Atom feed
From: Siddhesh Poyarekar <siddhesh@redhat.com>
To: Pedro Alves <alves.ped@gmail.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>,
	       Siddhesh Poyarekar <siddhesh.poyarekar@gmail.com>,
	       "Joseph S. Myers" <joseph@codesourcery.com>,
	       GNU C Library <libc-alpha@sourceware.org>,
	carlos@redhat.com,        gdb@sourceware.org
Subject: Re: Actually setting up patchwork on sourceware
Date: Fri, 23 May 2014 12:50:00 -0000	[thread overview]
Message-ID: <20140523125151.GF14500@spoyarek.pnq.redhat.com> (raw)
In-Reply-To: <5371DF7C.7060408@gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1260 bytes --]

On Tue, May 13, 2014 at 10:01:48AM +0100, Pedro Alves wrote:
> On 05/13/14 07:04, Siddhesh Poyarekar wrote:
> > On Mon, May 12, 2014 at 01:17:26PM -0400, Frank Ch. Eigler wrote:
> >> Hi -
> >>
> >>> [...]  Frank, did you get a chance to look at it?  I have
> >>> documented[1] the process I had followed to do the patchwork setup
> >>> on my host.  [...]
> >>
> >> Sorry, I was under the impression that y'all were still choosing
> >> between patchwork and other alternatives.  (Maybe "y'all" included gdb
> >> folks, cc:'d.)  We'd love not to have to have N new but similar
> >> widgets running on sourceware.
> > 
> > I had set up a test instance for gdb folks too and Gary had requested
> > that I also migrate the gdb instance from my server to sourceware
> > since it would take a while for gdb to decide on their final choice,
> > so I'm not sure if it's worth our while to wait for that to happen.
> 
> Yes, please migrate gdb's too.  At least myself, I'm finding the
> gdb instance useful.  As long as it exists, might as well have it set
> up alongside glibc's.

That's great.  Given that 10 days have past since your response, is it
safe to assume that nobody in the gdb community is opposed to using
patchwork?

Siddhesh

[-- Attachment #2: Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-05-23 12:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20140402055454.GB23931@spoyarek.pnq.redhat.com>
     [not found] ` <Pine.LNX.4.64.1405121520130.371@digraph.polyomino.org.uk>
     [not found]   ` <CAAHN_R0zS6_A=HfA22966G7xvvzuJCdMD6jp4x5cbPq4v_wy2w@mail.gmail.com>
2014-05-12 17:17     ` Frank Ch. Eigler
2014-05-13  6:03       ` Siddhesh Poyarekar
2014-05-13  9:02         ` Pedro Alves
2014-05-23 12:50           ` Siddhesh Poyarekar [this message]
2014-05-23 16:23             ` 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=20140523125151.GF14500@spoyarek.pnq.redhat.com \
    --to=siddhesh@redhat.com \
    --cc=alves.ped@gmail.com \
    --cc=carlos@redhat.com \
    --cc=fche@redhat.com \
    --cc=gdb@sourceware.org \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=siddhesh.poyarekar@gmail.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