From: Daniel Jacobowitz <drow@false.org>
To: "André Pönitz" <apoenitz@trolltech.com>
Cc: gdb-patches@sources.redhat.com
Subject: Re: gdb sources
Date: Fri, 19 Sep 2008 14:45:00 -0000 [thread overview]
Message-ID: <20080919144422.GA32108@caradoc.them.org> (raw)
In-Reply-To: <200809191612.23617.apoenitz@trolltech.com>
It looks like you don't have a copyright assignment or employer
disclaimer on file. Is that correct? If so, we should sort it out
now before you contribute anything larger.
On Fri, Sep 19, 2008 at 04:12:14PM +0200, André Pönitz wrote:
> Ok. Something tiny attached for starters. It is as harmless as it can be.
> I hope this is uncontroversial, but before going further into this
> direction I have two related questions:
>
> 1. How would the prefered way to call, say, xfree on a 'conceptionally const
> char *' item look like? Are casts to non-const (void *) acceptable
> here?
Probably acceptable, but if you know it is allocated by xfree, should
it really be returned as const?
> 2. Recording every such change in the ChangeLog basically duplicates
> the work. Are there any shortcuts available/acceptable?
If you have to update the call sites, you can say "all callers
updated" or something like that in the changelog entry, though if any
of the changes are more than mechanical then it's better to list
the complicated ones explicitly. But for just a change to a prototype
and a definition, I think the changelog entry is still appropriate.
BTW, your changelog is too verbose in another way; there is normally
only one starred entry for a file and you can combine similar changes.
Like this:
* symfile.c (allocate_symtab, allocate_psymtab, free_named_symtabs)
(deduce_language_from_filename): Accept a const argument.
Please use diff -up for patches; with the default diff arguments, it's
impossible to see what you've changed.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2008-09-19 14:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200809121713.09226.apoenitz@trolltech.com>
[not found] ` <20080912153534.GA13672@caradoc.them.org>
2008-09-19 14:13 ` André Pönitz
2008-09-19 14:45 ` Daniel Jacobowitz [this message]
2008-09-19 15:21 ` André Pönitz
2008-09-19 15:26 ` Daniel Jacobowitz
2008-09-19 15:46 ` André Pönitz
2008-09-19 16:25 ` Daniel Jacobowitz
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=20080919144422.GA32108@caradoc.them.org \
--to=drow@false.org \
--cc=apoenitz@trolltech.com \
--cc=gdb-patches@sources.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