search for: source_dirs

tags 688308 +patch thanks A lot of /docs/ is pretty low-level and not all that interesting to be installed by the packages. However some of it is, and in particular some is referenced from the manpages. I've cherry-picked the bits which I think are most interesting in that context. Patch below. 8<--------------- commit 7f8ac283e684b7c713d52ed845cab0704a97abab Author: Ian Campbell <ijc

On UNIX, I am executing an rsync command, from within a script. The command goes something like this: /usr/bin/rsync --verbose --progress --stats --compress --recursive --times --perms --links --safe-links source_dir/ user at target_machine:/parent_path/source_dir In other words, I am replicating source_dir on a remote machine. It ends up next to a lot of sibling, directories, like this: On

I have a function: source_dir <- function(path, pattern = "\\.[rR]$", chdir = TRUE) ... documented with ... \usage{source_dir(path, pattern="\\.[rR]$", chdir=TRUE)} ... But I get Codoc mismatches from documentation object 'source_dir': source_dir Code: function(path, pattern = "\\.[rR]$", chdir = TRUE) Docs: function(path, pattern =

tags 407143 +patch thanks On Fri, 2013-08-16 at 14:42 +0100, Ian Campbell wrote: > tags 688308 +patch > thanks > > A lot of /docs/ is pretty low-level and not all that interesting to be > installed by the packages. However some of it is, and in particular some > is referenced from the manpages. I've cherry-picked the bits which I > think are most interesting in that

Guys, I''m working with the new RadRails release (0.5.3), which has a very nifty inclusion of ri courtesy of RDT. Problem is, although I''ve generated rdoc for all installed gems with "gem rdoc --all", it''s not accessible through ri. I see some posts here and there about rimport...is this still the necessary way to incorporate the rails rdoc into ri?

I'm using a little shell script: BUILD_ROOT=/home/llvm-1.7/cfrontend PREFIX="$BUILD_ROOT/install" LOCAL_BUILD_DIR="$BUILD_ROOT/build" SOURCE_DIR="$BUILD_ROOT/src" echo $__me: Building $TARGET echo $__me: BUILD_ROOT == $BUILD_ROOT echo $__me: SOURCE_DIR == $SOURCE_DIR echo $__me: LOCAL_BUILD_DIR == $LOCAL_BUILD_DIR echo $__me: PREFIX == $PREFIX

Greg Pettyjohn <gregp at ccs.neu.edu> writes: > Is the MinGW user's list on the web? Look on www.mingw.org -> mailing list > Can you give me a link to the thread? Sorry, no time for that. Once on the mailing list archives, do a search for 'configure'. > (What's IIRC?) If I Remember Correctly. By the way, what's your configure command? -- Oscar

Is the MinGW user's list on the web? Can you give me a link to the thread? (What's IIRC?) Thanks. On Sat, 22 Apr 2006, Oscar Fuentes wrote: > Greg Pettyjohn <gregp at ccs.neu.edu> writes: > > > I've blown a couple of weekends trying to build under MinGW. > > > > I can build the llvm tools with only a couple of minor hassles, but can't > > seem

Hi all, I'm running the following rsync job via cron: rsync --recursive --compress --human-readable --progress --update --perms --chmod=a-w -e "ssh -i /rsync-key" user@host:/source_dir/ /target_dir rsync: failed to set permissions on "/target_dir/.": Operation not permitted (1) rsync: failed to modify permissions on "/target_dir/.": Operation not permitted (1)

Hi there, I am using rsync to synchronize two folders. I have configured the log-format to my personal needs like this: --log-format="%f %t %o %l %P" I am also using the --delete flag to log deleted files as well. I have upgraded my rsync version to 2.6.9 when I figured out that starting with version 2.6.4 the log format had been enhanced to also include the "del."

I've been using CMake on my LLVM project for several years now (ever since I abandoned using SCons, and before that, autoconf). During that time I've grown to both love and hate CMake - that is, I love the idea, but hate the language and its limitations. However, due to the recent thread on this list, I realized that I wasn't the only person that felt that way - that there were a lot

Greg Pettyjohn <gregp at ccs.neu.edu> writes: > I'm using a little shell script: [snip] > confopts="--prefix=$PREFIX" > confopts="$confopts --disable-threads" > confopts="$confopts --disable-nls" > confopts="$confopts --disable-shared" > confopts="$confopts --enable-languages=c,c++" >

puppetlabs_spec_helper is a Rubygem to make writing and running module spec tests using rspec-puppet easier. It includes a set of common rake tasks and a spec_helper that correctly initializes puppet and rspec-puppet for testing. The code is available on github at http://github.com/puppetlabs/puppetlabs_spec_helper. Patches are welcome. To convert a module with existing spec tests to use the

Thank you Kevin. It seems that I misunderstood the purpose of this --delete-missing-args option. If someone has a good suggestion on how to rsync a list of files and delete from the destination any file that is not listed in --files-from, that would be welcome. Thanks, MI -------- Original Message -------- (Kevin Korb via rsync, 2019-04-23 14:11) > --files-from will delete files from

rsync Folks, The following explanatory text is by me and the patches are by Rowan McKenzie for use by the Advanced Scientific Computing group at CSIRO. This patch builds upon the --link-dest patch by Bryant Hansen (Thanks heaps!). 1. The original patch provided an alternate behaviour for rsync when using the --link-dest option. When there are identical files in the source and link-dest areas,

Hi all, I'm running rsync version 2.6.3 protocol version 28 on Solaris 8 and am having a problem. We have some scripts that wrap around rsync and generate a list of files to transfer from the sending system (regardless of whether that directory exists on the receiver). I was expecting rsync to fail when transferring files with a path that doesn't exist on the receiver (in fact

> On Jan 12, 2016, at 9:39 AM, Reid Kleckner <rnk at google.com> wrote: > > Sounds like a plan. > > Should we leave behind a simple ./configure script that checks for cmake, and if present, runs something like 'cmake -G"Unix Makefiles" .'? I think it's nice if the "standard" Unix way of building with "./configure && make"

This is odd: We're using rsync to mirror multiple directories from a server to two clients. The server is running Tru64 v5.1a, client A is running Redhat Linux 8.0, and client B is running Tru64 v4.0g. The mirrors for both clients are running at the same time interval (10 minutes, offset by 5 minutes). All machines are running rsync v2.5.6, and using ssh2 v3.2.3 as the

Moving to llvm-dev (I think this has gone a bit further than a patch review discussion) In hindsight I probably should have explained more of my thinking on this with the patch, or done an RFC on llvm-dev to start with. I’l do that now, and answer the questions along the way. I sent a separate email discussing Justin’s patch review feedback. In the build system today there is no strong

Memory leaks found by the tool--valgrind along with static reviewing. Based on Daivd''s branch ''integration-20130903''. Gui Hecheng (5): btrfs-progs:free local variable buf upon unsuccessful returns btrfs-progs:local variable memory freed btrfs-progs: missing tree-freeing statements added btrfs-progs:free the local list pending_list in btrfs_scan_one_dir