From: Brian Gladman <brg@gladman.plus.com>
To: Patrick Alken <patrick.alken@Colorado.EDU>
Cc: "gsl-discuss@sourceware.org" <gsl-discuss@sourceware.org>
Subject: Re: new GSL version
Date: Fri, 24 May 2013 21:12:00 -0000 [thread overview]
Message-ID: <519FD78F.7080405@gladman.plus.com> (raw)
In-Reply-To: <519FD288.8060200@colorado.edu>
On 24/05/2013 21:50, Patrick Alken wrote:
> Hi Brian,
>
> I admit I haven't followed the windows issues closely at all.
>
> Is the symlink problem part of the GSL repository, or is it a
> windows/bzr issue? In my current repository, I see the following symlinks:
>
>> find . -type l
> ./siman/.gitignore
> ./doc/.gitignore
> ./.gitignore
> ./gsl/.gitignore
>
> Is this what is causing you problems? I imagine all of these can be
> removed since we're not even using git anymore.
I think it is but I won't know for certain until we try it.
If these symlinks could be removed, I will then see if the errors I am
seeing go away.
> Regarding the windows bugs you've reported, are they in the bug tracker
> at all, or just floating around on the bug-gsl list? If they are not in
> the tracker, do you think you would be able to add them (or at least
> point me to the relevant bug-gsl dates), and if there are simple
> solutions, I could try fixing them early next week and sending you a
> test tarball file.
I sent the details to Rhys some time ago but I can document the one I
fixed again. I'll get back to you on this.
Brian
next prev parent reply other threads:[~2013-05-24 21:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-24 16:00 Patrick Alken
2013-05-24 18:51 ` Brian Gladman
2013-05-24 20:50 ` Patrick Alken
2013-05-24 21:12 ` Brian Gladman [this message]
[not found] ` <CAKDqugRByMUqy0s0r2trq=z3u3N4XkaCW=zANQ=MRDENB6dHig@mail.gmail.com>
2013-05-24 19:36 ` Patrick Alken
2013-05-26 7:28 ` Tuomo Keskitalo
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=519FD78F.7080405@gladman.plus.com \
--to=brg@gladman.plus.com \
--cc=gsl-discuss@sourceware.org \
--cc=patrick.alken@Colorado.EDU \
/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).