Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andy Wingo <wingo@igalia.com>
To: Doug Evans <xdje42@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH 1/9] Allow GDB to build against unreleased Guile 2.2
Date: Thu, 17 Apr 2014 09:04:00 -0000	[thread overview]
Message-ID: <87ppkgs4xc.fsf@igalia.com> (raw)
In-Reply-To: <m3eh12tsag.fsf@sspiff.org> (Doug Evans's message of "Sat, 12 Apr	2014 09:40:39 -0700")

Hi,

Thanks for the review.  I'll post a new patchset shortly incorporating
feedback.  Sorry for the gaffe with the changelogs.

On Sat 12 Apr 2014 18:40, Doug Evans <xdje42@gmail.com> writes:

> 2) The change to configure is small, so it's not a big a deal,
> but, for reference sake, the convention here is to not include changes
> to machine generated files in patches submitted to the list.
> Plus I wouldn't expect a change to the Copyright year in configure.

I edited the file manually as I don't have autoconf2.64 on my system,
hence the copyright year update.  I removed the copyright update from
the updated patchset, but kept the change to the generated configure
file as it's so trivial that I can only imagine autoconf producing
exactly those changes.  I can repost that patch without that change if
you like.

> btw, this patch is small enough to not require one, and while I wouldn't
> doubt that you have a copyright assignment for Guile changes :-), do you
> have one for gdb?  I can imagine having a blanket assignment for
> everything, just checking.

I was agnozing over having to do that when I found to my pleasant
surprise that Igalia already has a corporate assignment for GDB, made
when Sanjoy Das was doing the custom debug info JIT interface stuff a
couple years ago.  Hopefully that suffices.

Cheers,

Andy


  parent reply	other threads:[~2014-04-17  9:04 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-09 16:14 [PATCH 0/8] Cleanups to Guile extension interface Andy Wingo
2014-04-09 16:14 ` [PATCH 1/9] Allow GDB to build against unreleased Guile 2.2 Andy Wingo
2014-04-12 16:40   ` Doug Evans
2014-04-12 16:47     ` Doug Evans
2014-04-17  9:04     ` Andy Wingo [this message]
2014-04-09 16:14 ` [PATCH 8/9] Remove useless Guile SMOB marking functions Andy Wingo
2014-04-12 19:50   ` Doug Evans
2014-04-09 16:14 ` [PATCH 9/9] Remove a useless Guile finalizer Andy Wingo
2014-04-12 20:18   ` Doug Evans
2014-04-14 12:12     ` Ludovic Courtès
2014-04-14 21:39       ` Doug Evans
2014-04-15  9:29         ` Ludovic Courtès
2014-04-15 15:30           ` Doug Evans
2014-04-17 10:07     ` Andy Wingo
2014-04-09 16:14 ` [PATCH 6/9] Remove Guile GDB object property mechanism Andy Wingo
2014-04-12 19:23   ` Doug Evans
2014-04-17  9:54     ` Andy Wingo
2014-04-09 16:14 ` [PATCH 7/9] Remove Guile mark functions that don't mark anything Andy Wingo
2014-04-12 19:29   ` Doug Evans
2014-04-17  9:48     ` Andy Wingo
2014-04-20 19:34       ` Doug Evans
2014-04-22  7:40         ` Andy Wingo
2014-04-29 11:51         ` Ludovic Courtès
2014-04-09 16:14 ` [PATCH 4/9] Fix typos in documentation of Guile `execute' function Andy Wingo
2014-04-09 16:14 ` [PATCH 3/9] Fix excess parentheses in Guile extension examples Andy Wingo
2014-04-09 16:14 ` [PATCH 5/9] Rename "gsmob" in Guile interface to "gdb object" Andy Wingo
2014-04-12 18:46   ` Doug Evans
2014-04-17  9:39     ` Andy Wingo
2014-04-17  9:46       ` Eli Zaretskii
2014-04-09 16:14 ` [PATCH 2/9] Define and export Guile classes for all GDB object types Andy Wingo
2014-04-12 18:32   ` Doug Evans
  -- strict thread matches above, loose matches on Subject: below --
2014-04-09 16:09 [PATCH 0/8] Cleanups to Guile extension interface Andy Wingo
2014-04-09 16:09 ` [PATCH 1/9] Allow GDB to build against unreleased Guile 2.2 Andy Wingo

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=87ppkgs4xc.fsf@igalia.com \
    --to=wingo@igalia.com \
    --cc=gdb-patches@sourceware.org \
    --cc=xdje42@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