similar to: [feature request] Modify --backup option to make backups on source side, too

----- Weitergeleitete Nachricht von digulla@hepe.com ----- Datum: Mon, 15 Oct 2007 16:05:13 +0200 Von: Aaron Digulla <digulla@hepe.com> Antwort an: Aaron Digulla <digulla@hepe.com> Betreff: Re: [feature request] Modify --backup option to make backups on source side, too An: Matt McCutchen <hashproduct+rsync@gmail.com> Quoting Matt McCutchen

> It's done by the front-end. There are a variety of attributes and > mechanisms which are used to convolute data and marshall it through > call sites in an ABI-conformant manner. Oh dear. :-( Do the attributes change depending on the type? I would assume that attributes like "ccc" are type-invariant; i.e. every instantiation should use the C-calling convention, whatever

I have a package that can use rmpi, but works fine without it. None of the automatic test code invokes rmpi functionality. (One test file illustrates how to use it, but has quit() as its first command.) What's the best way to handle this? In particular, what is the appropriate form for upload to CRAN? When I omitted rmpi from the DESCRITPION file R CMD check gave <quote> * checking

I am considering installing a Puppet agent on a legacy server running an old, crappy, slow, leaky, yet important Java app. Nervous about introducing anything that might (further) destabilize the app. What are people''s experiences with Puppet in terms of resource usage (CPU/ memory/network/etc)? For starters will likely run it on the standard daemon schedule. Ultimately may want to control

If read.table() is defaulting to "character" instead of "factor" data type, shouldn't type.convert() also default to "character" in R 4.0.0? This would seem like a good time to change the default to type.convert(as.is=TRUE), to align it with the new default in read.table and data.frame. I think many R >=4.0.0 users would be happy with as.is=TRUE as the default

On Wednesday 18 February 2009 20:57:02 DeLesley Hutchins wrote: > > It's done by the front-end. There are a variety of attributes and > > mechanisms which are used to convolute data and marshall it through > > call sites in an ABI-conformant manner. > > Oh dear. :-( I think many people were confused by this at first but an excellent counter example was provided in a

> I think many people were confused by this at first but an excellent counter > example was provided in a previous thread: C99 ABIs can require that struct > return values are returned via a pointer to a preallocated struct passed as > an auxiliary argument *except* when you're talking about a C99 complex, in > which case the return value is conveyed in a completely different

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Welcome to the first release of the 3.1.0 development branch. This is an unstable release series intended only for use by testers and developers. We make no claims as to whether it even works. The purpose of the 3.1.x releases is similar to what we've used the 'alpha' tag for in the past. These are unstable, development releases that

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Welcome to the first release of the 3.1.0 development branch. This is an unstable release series intended only for use by testers and developers. We make no claims as to whether it even works. The purpose of the 3.1.x releases is similar to what we've used the 'alpha' tag for in the past. These are unstable, development releases that

Hello list, Is there a possibility to add entries to the winbindd_idmap.tdb manually? I know I can use tdbdump to see the entries, but is there a chance to modify? My problem is I have to map some uid to some Windows SID without using LDAP. On the other hand new user not having any uid in linux should map to the range of uid I defind by using idmap uid = 10000-20000 2nd Question: Is it

Dear Martin, Thank you for the well-reasoned response. I realized I was rather late to make this suggestion for 4.0.0, changing a somewhat low-level function that can indeed affect packages. I was just reviewing some R user scripts that were using type.convert(), mainly on data frames. In all cases, people were passing as.is=TRUE, so I was reminded that I would not be the only user who would

We have a local time server and all of our machines are pointed at it for the time. How can the clock drift by a day and a half? [root at devserver21 ~]# date Fri Aug 13 14:43:29 EDT 2010 [root at devserver21 ~]# rdate -s 192.168.1.67 [root at devserver21 ~]# date Thu Aug 12 07:02:39 EDT 2010 [root at devserver21 ~]# cat /etc/ntp.conf | grep -v ^# | grep -v ^$ restrict default nomodify notrap

>Another might be to introduce changes under feature flags to ease the revert/reintroduce/revert cycle. This is essentially the first guard. We plan to have flags/settings to control which types of outer loops are handled. The new code path is initially exclusive to outer loop vectorization. If we disable all types of outer loops (and that's the initial default), LV continues to be good

I think a modifier for filter rules that inhibits the --backup option for the particular line might be useful. for example I could have --filter='H,nb /.mozilla/firefox/xxxxx.default/Cache' or I could have --filter'+ /Documents' --filter'+,nb /.mozilla' (So my documents will be backed up to --backup-dir but my firefox profile will not)

I've finally read and answered most of the mails on this list. ?If you haven't received an answer to your question, resend it. There are a couple of tricky mbox issues left, but I'm not sure if I can do anything about them unless someone can show me how to reproduce the problems. There are quite a lot of new features in v1.1.2 actually. Most of them are in plugins so hopefully they

To revive the discussion around vectorizer testing, here's a quick sample of a few of the issues hit recently in the loop vectorizer.  I want to be careful to say that I am not stating these are the result of any recent work, just that they're issues that have been triaged down to the loop vectorizer doing something incorrect or questionable from a performance perspective.

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz http://dovecot.org/releases/1.1/alpha/dovecot-1.1.alpha1.tar.gz.sig This is the first alpha release of Dovecot v1.1. I hope that it stabilizes into final release within a few months. There are a lot of new features since v1.0. The most important ones are listed at the end of this post. This is the only v1.1.alpha announcement I send

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Tanya M. Lattner wrote: > There was much debate about which version control system to switch to > (please search the llvm-dev mailing list). Well, I would if it were searchable... > I think its best not to rehash this discussion. We have already begun the > steps to convert to SVN. I come from a different perspective. While I

I have a Proliant running Red Hat with the 2.6.9-5.ELsmp kernel. We have a Windows 2000 Server who's secondary disc drive is mounted on the Linux box via CIFS using the following command: /sbin/mount.cifs //w2000/docs /var/www/documents -o dir_mode=0777,file_mode=0444,gid=100,uid=501,username=winuser,password=winpass From time to time, for whatever reason, the Windows 2000 Server