From: Keith Rollin <keith.rollin@palmsource.com>
To: Christopher Faylor <cgf@alum.bu.edu>, gdb-patches@sources.redhat.com
Subject: Re: [PATCH] Various Windows support changes
Date: Wed, 21 Apr 2004 20:43:00 -0000 [thread overview]
Message-ID: <p06001f0fbcac896ed43a@[192.168.108.87]> (raw)
In-Reply-To: <20040420163507.GB22971@coe.bosbc.com>
Christopher,
Thanks for the reply. My responses are below:
At 12:35 PM -0400 4/20/04, Christopher Faylor wrote:
>1) It is a fairly large patch involving a few distinct fixes.
> It is much easier to review and install one patch which addresses
> one problem than it is to review one gigantic patch which addresses
> n problems. Would you consider sending this as multiple patches?
I remember reading that recommendation in the CONTRIBUTE document,
but it wasn't clear to me how to provide multiple patches. I don't
know how to create them -- how do I separate my changes?
>2) Please don't send compressed patches here. Just send your patch
> and ChangeLog as plain text.
OK. The CONTRIBUTE document said "We accept patches as ... gzipped
text", so I thought what I did was OK.
>3) Please send patches against CVS rather than a gdb release.
> Patches generated against CVS are more likely to apply cleanly.
> As it turns out, your patch installed ok with the exception of
> your change to version.in. However, it is always a little more
> comforting to see a patch apply without the fuzz and offset warnings
> from patch.
I was leery of sending in patches against gdb 6.0, especially when
6.1 had just been released. However, I've never used CVS, and so
don't know how to perform what you ask. If needed, of course, I
could learn.
>4) It doesn't look like Palm has an assignment with the FSF.
> Jim? Can you send him an assignment form?
The CONTRIBUTE document said that I could get a form from some cited
web site, but I was unable to actually find the form. In lieu of
that, the CONTRIBUTE document said that such a form was not necessary
for small fixes, for which I'd hoped my changes qualified. If not,
I'll look for Jim to send me an assignment form.
>5) The ChangeLog is a little non-standard.
> Please use capitalization and present tense, i.e., "Add TEMP and
>TMP" rather
> than "added TEMP and TEMP".
Thanks. I'll keep that in mind.
>I do appreciate all of the work that went into this patch. The only
>real stumbling block here is the lack of an FSF assignment.
At this point, it's not clear to me if your points above are advice
for any subsequent submissions, or if I need to address them for this
submission. You noted that you'd already applied the patch, so I'm
thinking the former. But if the latter, then let me know and I'll
tweak things.
In either case, I'll look for the assignment for to arrive and get it
back to you. I'll assume that instructions on what to do with the
form after I'm done with it will come with the form.
-- Keith Rollin
-- Development Tools engineer
next prev parent reply other threads:[~2004-04-21 20:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-19 23:37 Keith Rollin
2004-04-20 16:35 ` Christopher Faylor
2004-04-21 20:43 ` Keith Rollin [this message]
2004-04-21 21:24 ` [PATCH] Various Windows support changes (assignment needed) Christopher Faylor
2004-04-28 17:55 ` Keith Rollin
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='p06001f0fbcac896ed43a@[192.168.108.87]' \
--to=keith.rollin@palmsource.com \
--cc=cgf@alum.bu.edu \
--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