From: "Dr. Volker Zell" <dr.volker.zell@oracle.com>
To: cygwin-apps@cygwin.com
Subject: Re: setup-2.ini problems/anomalies
Date: Fri, 15 Aug 2008 14:00:00 -0000 [thread overview]
Message-ID: <7z4p5m8jmd.fsf@vzell-de.de.oracle.com> (raw)
In-Reply-To: <20080815114846.GI21040@calimero.vinschen.de> (Corinna Vinschen's message of "Fri, 15 Aug 2008 13:48:46 +0200")
>>>>> Corinna Vinschen writes:
> That's probably a result of using only the latest package in the
> release-2 area when creating the union fs. They should be fixed by
> either making all the test versions curr, or by copying the curr
> versions over from release to release-2. Can you do that at one
> point, Volker? I need some time for debugging now.
Done for emacs*, xemacs* and grace packages.
Ciao
Volker
next prev parent reply other threads:[~2008-08-15 14:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-15 10:02 Dr. Volker Zell
2008-08-15 11:48 ` Corinna Vinschen
2008-08-15 14:00 ` Dr. Volker Zell [this message]
2008-08-15 14:05 ` Corinna Vinschen
2008-08-15 15:20 ` Christopher Faylor
2008-08-15 15:26 ` Corinna Vinschen
2008-08-15 16:22 ` Christopher Faylor
2008-08-15 15:14 ` Christopher Faylor
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=7z4p5m8jmd.fsf@vzell-de.de.oracle.com \
--to=dr.volker.zell@oracle.com \
--cc=cygwin-apps@cygwin.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).