public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Enze Li <enze.li@hotmail.com>
To: Tom de Vries <tdevries@suse.de>, gdb-patches@sourceware.org
Cc: "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: [PATCH][gdb/build] Handle deprecation of scm_install_gmp_memory_functions
Date: Thu, 07 Jul 2022 16:30:27 +0800	[thread overview]
Message-ID: <TYCP286MB216310E3E8BD66C6772A23C8F0839@TYCP286MB2163.JPNP286.PROD.OUTLOOK.COM> (raw)
In-Reply-To: <b81c91fd-65bd-2795-10e1-bec7f5763d33@suse.de>

On Thu, 2022-07-07 at 10:20 +0200, Tom de Vries wrote:
> On 7/7/22 10:14, Enze Li wrote:
> > > 
> > > Co-Authored-By: Tom de Vries <tdevries@suse.de>
> > ^^^^^^^^^^^^^^
> > This part confused me.  Is it necessary to include such a line when
> > the
> > author of the patch is the same person?
> > 
> 
> No, indeed it's not necessary in such a case.
> 
> However, that is not the case here, because I'm not the (main)
> author:
> ...
> $ git show --pretty=fuller -s
> commit b47665709cabeb064cd57e1bf21b95d92c68be4e (HEAD -> fix
> -guile-build)
> Author:     Ludovic Courtès <ludo@gnu.org>
> AuthorDate: Thu Jul 7 08:20:28 2022 +0200
> Commit:     Tom de Vries <tdevries@suse.de>
> CommitDate: Thu Jul 7 09:54:52 2022 +0200
> 
>      [gdb/build] Handle deprecation of
> scm_install_gmp_memory_functions
> ...
> 

Thanks for your explanation.  I was just curious about this. :-)

Cheers!
Enze



  reply	other threads:[~2022-07-07  8:30 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-07  7:58 Tom de Vries
2022-07-07  8:14 ` Enze Li
2022-07-07  8:20   ` Tom de Vries
2022-07-07  8:30     ` Enze Li [this message]
2022-07-08 14:03 ` [committed][gdb/build] " Tom de Vries

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=TYCP286MB216310E3E8BD66C6772A23C8F0839@TYCP286MB2163.JPNP286.PROD.OUTLOOK.COM \
    --to=enze.li@hotmail.com \
    --cc=gdb-patches@sourceware.org \
    --cc=ludo@gnu.org \
    --cc=tdevries@suse.de \
    /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).