From: Jonathan Larmour <jlarmour@redhat.com>
To: "Lewin A.R.W. Edwards" <larwe@larwe.com>
Cc: ecos-discuss@sourceware.cygnus.com
Subject: Re: [ECOS] dl_edb7xxx patch for cygwin
Date: Tue, 27 Mar 2001 16:41:00 -0000 [thread overview]
Message-ID: <3AC1334B.92E15070@redhat.com> (raw)
In-Reply-To: <4.3.2.7.2.20010327190731.0281e7a8@mail.larwe.com>
"Lewin A.R.W. Edwards" wrote:
>
> Hi Jonathan,
>
> > > Is this worth submitting as a patch? I can't see any significant loss of
> > > amenity from these patches.
> >
> >If you wrap the changes in #ifdef __CYGWIN__ I'll certainly be happy to
> >apply them.
>
> OK, how do I prepare and submit the patches? I may as well look at a couple
> of other little things while I'm in there.
I'm not quite sure what you mean. But doing a "cvs diff -u -p" against
current cvs is the way to generate them. Include a ChangeLog entry as well,
but just include that as text, not as part of the diff.
I should warn you that if changes are large we'll need a copyright
assignment.
Jifl
--
Red Hat, Rustat House, Clifton Road, Cambridge, UK. Tel: +44 (1223) 271062
Maybe this world is another planet's Hell -Aldous Huxley || Opinions==mine
prev parent reply other threads:[~2001-03-27 16:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-26 9:32 Lewin A.R.W. Edwards
2001-03-27 7:05 ` Jonathan Larmour
2001-03-27 16:09 ` Lewin A.R.W. Edwards
2001-03-27 16:41 ` Jonathan Larmour [this message]
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=3AC1334B.92E15070@redhat.com \
--to=jlarmour@redhat.com \
--cc=ecos-discuss@sourceware.cygnus.com \
--cc=larwe@larwe.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).