From: "Prafulla Thakare" <Prafulla.Thakare@kpitcummins.com>
To: "Nick Clifton" <nickc@redhat.com>
Cc: <binutils@sourceware.org>
Subject: RE: Contributing the Unifile utility for merging Mot or Hex files.
Date: Thu, 02 Apr 2009 09:23:00 -0000 [thread overview]
Message-ID: <82C3BC9106BCE149B63464D79D0A22FD0A077EC2@sohm.kpit.com> (raw)
In-Reply-To: <49D38509.6030109@redhat.com>
Nick Clifton wrote:
> I think that option 2 is the one that I prefer.
Thank you for your feedback.
We will now develop a patch to integrate the 'unifile' utility with
linker.
Regards,
Prafulla
prev parent reply other threads:[~2009-04-02 9:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-25 11:20 Prafulla Thakare
2009-04-01 15:15 ` Nick Clifton
2009-04-02 9:23 ` Prafulla Thakare [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=82C3BC9106BCE149B63464D79D0A22FD0A077EC2@sohm.kpit.com \
--to=prafulla.thakare@kpitcummins.com \
--cc=binutils@sourceware.org \
--cc=nickc@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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).