From: Masatoshi SEKI <m_seki@mva•biglobe.ne.jp>
To: ruby-dev@ruby-lang.org (ruby developers list)
Subject: [ruby-dev:44584] Re: [Ruby 1.9 - Bug #5419] FileUtils.cp_rの:preserveの動作
Date: Fri, 7 Oct 2011 20:13:50 +0900 [thread overview]
Message-ID: <9D0B5A0E-0A72-420A-ACE7-35AF74B6B4A4@mva.biglobe.ne.jp> (raw)
In-Reply-To: <redmine.journal-21218.20111007171654@ruby-lang.org>
咳といいます。
On 2011/10/07, at 17:16, Nobuyoshi Nakada wrote:
>
>
> その「もっとかっこいい方法」というのをちょっと教えて下さい。
ほんというと、よくわかってません。
木の辿りの帰りがけにmetadata_copyするのか、あるいは、あとでやるキューをつくるのか...
fu_each_src_destを二回まわるほうがずっと良いのかも。
next prev parent reply other threads:[~2011-10-07 11:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-07 7:46 [ruby-dev:44581] [Ruby 1.9 - Bug #5419][Open] FileUtils.cp_rの:preserveの動作 Masatoshi Seki
2011-10-07 8:16 ` [ruby-dev:44582] [Ruby 1.9 - Bug #5419] FileUtils.cp_rの:preserveの動作 Nobuyoshi Nakada
2011-10-07 11:13 ` Masatoshi SEKI [this message]
2011-10-07 8:17 ` [ruby-dev:44583] [Ruby 1.9 - Bug #5419][Assigned] FileUtils.cp_rの:preserveの動作 Nobuyoshi Nakada
2011-10-07 11:14 ` [ruby-dev:44585] " Masatoshi SEKI
2018-05-16 8:40 ` [ruby-dev:50542] [Ruby trunk Bug#5419][Closed] FileUtils.cp_rの:preserveの動作 mame
2018-05-16 9:13 ` [ruby-dev:50544] [Ruby trunk Bug#5419] FileUtils.cp_rの:preserveの動作 knu
2018-05-16 9:19 ` [ruby-dev:50545] " knu
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-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.ruby-lang.org/en/community/mailing-lists/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9D0B5A0E-0A72-420A-ACE7-35AF74B6B4A4@mva.biglobe.ne.jp \
--to=ruby-dev@ruby-lang.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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).