From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-patches@ecos.sourceware.org
Subject: [Bug 1001952] New: ConfigTool - Allow build environment to change version identification string
Date: Fri, 28 Feb 2014 10:02:00 -0000 [thread overview]
Message-ID: <bug-1001952-104@http.bugs.ecos.sourceware.org/> (raw)
Please do not reply to this email, use the link below.
http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001952
Bug ID: 1001952
Summary: ConfigTool - Allow build environment to change version
identification string
Product: eCos
Version: CVS
Target: All
Architecture/Host HostOS: Win XP/7
OS:
Status: UNCONFIRMED
Severity: enhancement
Priority: low
Component: Patches and contributions
Assignee: unassigned@bugs.ecos.sourceware.org
Reporter: andy@xylanta.com
CC: ecos-patches@ecos.sourceware.org
Created attachment 2473
--> http://bugs.ecos.sourceware.org/attachment.cgi?id=2473&action=edit
Allow build environment to change version identification string
This simple patch makes it easier to change the version identification string
from the build environment allowing custom builds identified as such. This
should be platform independent.
--
You are receiving this mail because:
You are on the CC list for the bug.
reply other threads:[~2014-02-28 10:02 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bug-1001952-104@http.bugs.ecos.sourceware.org/ \
--to=bugzilla-daemon@bugs.ecos.sourceware.org \
--cc=ecos-patches@ecos.sourceware.org \
/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).