From: Arun Isaac <arunisaac@systemreboot.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 28281@debbugs.gnu.org
Subject: [bug#28281] [PATCH] gnu: Add os-prober.
Date: Mon, 11 Sep 2017 05:05:54 +0530 [thread overview]
Message-ID: <24e1529f.AEAAPzHdNuUAAAAAAAAAAAPmNSgAAAACwQwAAAAAAAW9WABZtcxv@mailjet.com> (raw)
In-Reply-To: <87k2165lry.fsf@gnu.org>
>> I am trying to do
>>
>> cp -r /some/directory/* destination
>>
>> To do this, I used `find-files-non-recursive' to get all files in
>> /some/directory/ and applied `copy-recursively' on each one of them.
>>
>> Do you have a better way of doing this in mind?
>
> Would (copy-recursively "/some/directory" destination) work for you?
No, it wouldn't. That would recreate /some/directory at the
destination. I only want the files inside /some/directory to be copied,
not /some/directory itself.
next prev parent reply other threads:[~2017-09-10 23:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170909171635.7968-1-arunisaac@systemreboot.net>
2017-09-09 17:24 ` [bug#28281] [PATCH] gnu: Add os-prober Arun Isaac
[not found] ` <e7d9c9ca.AEQAP00oGCwAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZtCPY@mailjet.com>
2017-09-10 13:05 ` Ludovic Courtès
2017-09-10 16:02 ` Arun Isaac
[not found] ` <403302d1.ADkAAC_e-_IAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZtWIT@mailjet.com>
2017-09-10 20:41 ` Ludovic Courtès
2017-09-10 23:35 ` Arun Isaac [this message]
[not found] ` <5dc91a20.AEAAPzHdNuYAAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZtcxv@mailjet.com>
2017-09-11 7:28 ` Ludovic Courtès
2017-09-11 17:23 ` Arun Isaac
[not found] ` <207deec4.AEAAP2Xyu24AAAAAAAAAAAOzWv8AAAACwQwAAAAAAAW9WABZtsaB@mailjet.com>
2017-09-11 20:20 ` Ludovic Courtès
2017-09-13 23:22 ` bug#28281: " Arun Isaac
2017-08-29 19:06 [bug#28281] " Arun Isaac
2017-08-31 13:25 ` Ludovic Courtès
2017-08-31 17:41 ` Arun Isaac
2017-09-09 17:16 ` Arun Isaac
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=24e1529f.AEAAPzHdNuUAAAAAAAAAAAPmNSgAAAACwQwAAAAAAAW9WABZtcxv@mailjet.com \
--to=arunisaac@systemreboot.net \
--cc=28281@debbugs.gnu.org \
--cc=ludo@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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
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.