Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Andrew Cagney <ac131313@ges.redhat.com>
To: Kevin Buettner <kevinb@redhat.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: [PATCH RFC] Character set support
Date: Fri, 20 Sep 2002 09:08:00 -0000	[thread overview]
Message-ID: <3D8B47E9.5020100@ges.redhat.com> (raw)
In-Reply-To: <1020920071148.ZM24070@localhost.localdomain>

> On Sep 19,  9:12pm, Andrew Cagney wrote:
> 
> 
>> 2002-09-09  Elena Zannoni  <ezannoni@redhat.com>
>> 
>>          From: Emmanuel Thome'  <thome@lix.polytechnique.fr>
>>          * top.c (init_main): Set rl_terminal_name.
>> 
>> to reflect both who committed and who created the change.
> 
> 
> Yes, I do it that way too from time to time usually for smaller
> changes that I might have to adapt somewhat.  Jim's work is much more
> substantial and only minor changes were required.  I felt that Jim's
> name should be prominent in the ChangeLog for this change.

In the above, Emmanuel's name is very prominant.  It was their patch 
that was committed.

The place to give credit for a work is either the top of a new file, 
and/or in the doco.  Suggest updating the (C) entry to include:

	Contributed by Red Hat, Inc.
	Written by Jim Blandy.

10 years from now, people won't be looking in the ChangeLog.

> If you really need to know who committed a change, the CVS logs and
> mailing list traffic are available.  Also, I believe there is ample
> precedent in other projects (e.g. gcc) for the way I did things.

The accepted GDB convention is per the above.  It means that the 
ChangeLog stands on its own and does not depend on access to either the 
CVS repository or the mailing lists.  It leaves no confusion over who 
committed and who authored the change.

>> Did the WCHAR problem get resolved?
> 
> 
> Yes, in the sense that we're taking Jim's patch as-is and we'll
> worry about wchar_t changes at some later date.
> 
> See http://sources.redhat.com/ml/gdb-patches/2002-09/msg00261.html

Can you please at least create a bug report ``some later date'' work can 
be tracked?

Andrew



  reply	other threads:[~2002-09-20 16:08 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-12 17:31 Kevin Buettner
2002-09-12 17:41 ` Daniel Jacobowitz
2002-09-12 20:24   ` Jim Blandy
2002-09-12 20:45     ` Andrew Cagney
2002-09-13 10:05       ` Jim Blandy
2002-09-13 11:39         ` Andrew Cagney
2002-09-13 19:06           ` Jim Blandy
2002-09-16 22:25             ` Andrew Cagney
2002-09-19 12:52               ` Jim Blandy
2002-09-19 13:27                 ` Kevin Buettner
2002-09-20 13:49                   ` Eli Zaretskii
2002-09-13  7:02     ` Daniel Jacobowitz
2002-09-13 10:16       ` Jim Blandy
2002-09-13 10:33         ` Daniel Jacobowitz
2002-09-13 11:42           ` Andrew Cagney
2002-09-13 12:11             ` Kevin Buettner
2002-09-13 12:15               ` Daniel Jacobowitz
2002-09-12 17:53 ` Andrew Cagney
2002-09-12 18:08   ` Kevin Buettner
2002-09-19 17:36 ` Kevin Buettner
2002-09-19 17:46   ` Kevin Buettner
2002-09-19 18:12   ` Andrew Cagney
2002-09-20  0:12     ` Kevin Buettner
2002-09-20  9:08       ` Andrew Cagney [this message]
2002-09-20 14:58         ` Kevin Buettner
2002-09-20 16:33           ` Andrew Cagney
2002-09-21  1:26           ` Eli Zaretskii
2002-09-20 16:55         ` Kevin Buettner
2002-09-20  8:59 ` Eli Zaretskii
2002-09-20 17:34   ` Kevin Buettner

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=3D8B47E9.5020100@ges.redhat.com \
    --to=ac131313@ges.redhat.com \
    --cc=gdb-patches@sources.redhat.com \
    --cc=kevinb@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