From: Jeff Law <law@redhat.com>
To: Eric Gallager <egall@gwmail.gwu.edu>, gcc-patches@gcc.gnu.org
Subject: Re: [PATCH, contrib] download_prerequisites: check for existing symlinks before making new ones
Date: Wed, 13 Jul 2016 21:36:00 -0000 [thread overview]
Message-ID: <6d8cc2be-c68d-81f9-2274-6a12628b8caa@redhat.com> (raw)
In-Reply-To: <CAMfHzOtL-nbQe5OUxyFyS2RfLia_PDyY4ZOokV81iGn8Km5iHA@mail.gmail.com>
On 06/27/2016 08:10 PM, Eric Gallager wrote:
> The last time I ran ./contrib/download_prerequisites, I already had
> previous symlinks set up from a previous run of the script, so `ln`
> followed the existing symlinks and created the new ones in the
> directories to which the symlinks pointed. This patch should fix that
> by removing the old symlinks before creating new ones. (For some
> reason the `-f` flag to `ln` that was already there wasn't enough for
> me.) Tested by running the script and ensuring that the new isl
> symlink pointed to the correct directory, and that there were no bad
> symlinks in the old isl directory. Could someone commit this trivial
> patch for me, or something like it? I don't have write access.
I'd really rather know why the "-f" flag didn't work for you. The whole
point of -f is to remove the destination file first.
Jeff
next prev parent reply other threads:[~2016-07-13 21:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 2:38 Eric Gallager
2016-07-13 21:36 ` Jeff Law [this message]
2016-07-14 10:57 ` Eric Gallager
2016-07-14 13:54 ` NightStrike
2016-07-14 17:24 ` Jeff Law
2016-07-14 19:57 ` Eric Gallager
2016-07-21 17:10 ` Jeff Law
2016-07-21 19:39 ` Eric Gallager
2016-08-03 16:12 ` Jeff Law
2016-07-14 13:53 ` NightStrike
2016-07-21 18:15 Bernd Edlinger
2016-07-22 22:28 ` Jeff Law
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=6d8cc2be-c68d-81f9-2274-6a12628b8caa@redhat.com \
--to=law@redhat.com \
--cc=egall@gwmail.gwu.edu \
--cc=gcc-patches@gcc.gnu.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).