> From: DJ Delorie <d...@redhat.com> > Cc: gcc-patches@gcc.gnu.org, gdb-patc...@sourceware.org > Date: Fri, 19 May 2017 21:25:56 -0400 > > Fix committed.
Thanks! Pedro, how do we make this propagated to the GDB repository? > As Pedro noted, the correct way to request a change is > to make the change in your local checked out repo, and run "svn diff" > (or "git diff"). My problem is, I don't have a GCC repository, so doing the above means checking it out, which takes a _very_ long time here. And the patch I was thinking about is not the one you eventually committed anyway, which is to be expected, since I have no idea about the various dependencies between the projects that use the common configure infrastructure and about how things are done to keep all the user projects in sync. IOW, not everyone who reports a problem can necessarily provide a patch. The fact that you know too much about my abilities in other projects doesn't (or shouldn't) change that ;-) > The easier you can make it for the maintainer (me!), the more likely > your patch will get handled quickly. I know. I was trying to make it as easy as I possibly could, given the level of my knowledge in this area.
