All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Vladimir 'φ-coder/phcoder' Serbinenko" <phcoder@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: [PATCH] fix removal of {cpu,machine} links on mingw/msys
Date: Sat, 18 Jan 2014 19:39:22 +0100	[thread overview]
Message-ID: <52DACA5A.9040601@gmail.com> (raw)
In-Reply-To: <20140118223213.7027d50d@opensuse.site>

[-- Attachment #1: Type: text/plain, Size: 1008 bytes --]

On 18.01.2014 19:32, Andrey Borzenkov wrote:
> В Sat, 18 Jan 2014 19:14:43 +0100
> Vladimir 'φ-coder/phcoder' Serbinenko <phcoder@gmail.com> пишет:
> 
>> On 28.12.2013 10:58, Andrey Borzenkov wrote:
>>> At least on Windows 2003 using "ln -s dir1 dir2" in msys shell succeeds,
>>> but results in what looks like hard link. Subsequent "rm -f dir2" (e.g.
>>> during second config.status invocation) fails. Check that we also can
>>> remove link to directory.
>>>
>>> Make it more clear in message that we are checking "ln -s".
>>>
>> Is there a way to reliably remove result of such test? We don't want to
>> leave a weird file after the test behind. Perhaps rm -rf since we know
>> that we test with newly-created directory?
> 
> Test does "rm -rf testdir" at the end already and it removes this.
> 
Go ahead then.
> 
> 
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
> 



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 274 bytes --]

      reply	other threads:[~2014-01-18 18:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-28  9:58 [PATCH] fix removal of {cpu,machine} links on mingw/msys Andrey Borzenkov
2014-01-18 18:14 ` Vladimir 'φ-coder/phcoder' Serbinenko
2014-01-18 18:32   ` Andrey Borzenkov
2014-01-18 18:39     ` Vladimir 'φ-coder/phcoder' Serbinenko [this message]

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=52DACA5A.9040601@gmail.com \
    --to=phcoder@gmail.com \
    --cc=grub-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.