public inbox for ecos-bugs@sourceware.org
help / color / mirror / Atom feed
From: bugzilla-daemon@bugs.ecos.sourceware.org
To: ecos-bugs@ecos.sourceware.org
Subject: [Bug 1001798] adding a package (epk-file) fails
Date: Fri, 22 Mar 2013 10:49:00 -0000	[thread overview]
Message-ID: <bug-1001798-13-OkHixEQCj4@http.bugs.ecos.sourceware.org/> (raw)
In-Reply-To: <bug-1001798-13@http.bugs.ecos.sourceware.org/>

Please do not reply to this email, use the link below.

http://bugs.ecos.sourceware.org/show_bug.cgi?id=1001798

--- Comment #7 from John Dallaway <john@dallaway.org.uk> ---
Bob

(In reply to comment #6)

> Sorry, I do not understand what you mean with your Comment 5.

The patch I attached to this bug report has now been incorporated into the eCos
CVS repository. The implication is that the next release or snapshot build of
the eCos Configuration Tool should no-longer exhibit the erroneous behaviour
you reported.

For avoidance of doubt, this issue has been resolved by modifying the eCos
Configuration Tool source code to accommodate the behaviour of Cygwin Tcl
8.5.x.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


  parent reply	other threads:[~2013-03-22 10:49 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-12 13:37 [Bug 1001798] New: " bugzilla-daemon
2013-03-12 13:39 ` [Bug 1001798] " bugzilla-daemon
2013-03-12 15:18 ` bugzilla-daemon
2013-03-12 17:34 ` bugzilla-daemon
2013-03-15 19:38 ` bugzilla-daemon
2013-03-15 19:40 ` bugzilla-daemon
2013-03-17 17:09 ` bugzilla-daemon
2013-03-18  8:54 ` bugzilla-daemon
2013-03-21 18:50 ` bugzilla-daemon
2013-03-22 10:49 ` bugzilla-daemon [this message]
2013-03-27 13:42 ` bugzilla-daemon
  -- strict thread matches above, loose matches on Subject: below --
2013-03-12 13:37 [Bug 1001798] New: " bugzilla-daemon
2013-03-12 13:39 ` [Bug 1001798] " bugzilla-daemon
2013-03-12 15:18 ` bugzilla-daemon

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-1001798-13-OkHixEQCj4@http.bugs.ecos.sourceware.org/ \
    --to=bugzilla-daemon@bugs.ecos.sourceware.org \
    --cc=ecos-bugs@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).