similar to: feature request: exclude from path

Displaying 20 results from an estimated 11000 matches similar to: "feature request: exclude from path"

2020 Aug 03
2
feature request: exclude from path
So I've gotten excluding paths to work as a standalone command. When I paste this into a script however, it ignores the exclusions. Any advice? rsync -aXvr --times --links --exclude={'*.vdi','*.vmdk','*.ova','*.qcow2','.config/discord/'} /home/path/ user at nas:/NAS/HOME/destination/ Are there supposed to be some kind of brackets around this?
2003 Sep 18
1
Save object R with tkgetSaveFile
HI, my question is about the function tkgetSavefile not save any file, for example the next script run OK but not save the file who i like to save, how i cant to save and object R with tkgetSaveFile, how i use the function save(objet, file="foo.R") with tkgetSaveFile ?What is the error?. I'm work with R 1.7.1 library(tcltk) x<-1 filetypes <- list("{Texto {.txt}} {Word
2013 Mar 11
4
[PATCH] tcm_vhost: Wait for pending requests in vhost_scsi_flush()
This patch makes vhost_scsi_flush() wait for all the pending requests issued before the flush operation to be finished. Changes in v4: - Introduce vhost_scsi_inflight - Drop array to track flush Changes in v3: - Rebase - Drop 'tcm_vhost: Wait for pending requests in vhost_scsi_clear_endpoint()' in this series, we already did that in 'tcm_vhost: Use vq->private_data to indicate
2013 Mar 11
4
[PATCH] tcm_vhost: Wait for pending requests in vhost_scsi_flush()
This patch makes vhost_scsi_flush() wait for all the pending requests issued before the flush operation to be finished. Changes in v4: - Introduce vhost_scsi_inflight - Drop array to track flush Changes in v3: - Rebase - Drop 'tcm_vhost: Wait for pending requests in vhost_scsi_clear_endpoint()' in this series, we already did that in 'tcm_vhost: Use vq->private_data to indicate
2019 Nov 18
30
RFC: Moving toward Discord and Discourse for LLVM's discussions
Hello everyone, *Short version:*I've set up an LLVM Discord server for real time chat (similar to IRC) and an LLVM Discourse server for forums (similar to email lists): https://discord.gg/xS7Z362 https://llvm.discourse.group/ Please join and use these new services. They are only partially set up and still very new, so don't hesitate to improve them and/or reach out to this thread with
2007 Jul 05
4
Me again, about the horrible documentation of tcltk
How on Earth can I know what are the arguments of any of the functions of the tcl/tk package? I tried hard to find, using all search engines available, looking deep into keywords of R, python's tkinter and tcl/tk, but nowhere I found anything remotely similar to a help. For example, what are the possible arguments to tkgetOpenFile? I know that this works: library(tcltk) filename <-
2019 Nov 19
3
Fwd: RFC: Moving toward Discord and Discourse for LLVM's discussions
But is it better or worse than IRC in this regard? On Mon, Nov 18, 2019 at 10:49 PM Daniel Chapiesky via llvm-dev < llvm-dev at lists.llvm.org> wrote: > > > ---------- Forwarded message --------- > From: Daniel Chapiesky <dchapiesky2 at gmail.com> > Date: Tue, Nov 19, 2019 at 1:48 AM > Subject: Re: [llvm-dev] RFC: Moving toward Discord and Discourse for >
2019 Nov 18
5
[cfe-dev] RFC: Moving toward Discord and Discourse for LLVM's discussions
FWIW I'm a fan of using open-source stuff for open-source projects. Discourse looks open source, but Discord doesn't as far as I can tell (?). On Mon, Nov 18, 2019 at 3:15 AM Chandler Carruth via cfe-dev < cfe-dev at lists.llvm.org> wrote: > Hello folks, > > I sent the message quoted below to llvm-dev@ just now, but it applies to > the whole community so sending an FYI
2016 Apr 01
6
Clang project renamed
Hi everyone, There are a number of issues with the current name of the Clang project: * It is prone to incorrect type setting, typically as CLang, CLANG, or most commonly c̦҉̫̘̺̹̖̗͒͆͋̈̃̇߯l߲҉̷̡̰̖͈̤̺͒҆̾̚͡͝a̺̹͍̔߭͠ͅn͋́͡g̱߫̉ * The C++ compiler ends in the string "g++", which causes problems for compiler wrapper scripts * The name has been used by a kickstarter project
2019 Nov 18
3
RFC: Moving toward Discord and Discourse for LLVM's discussions
On Mon, 18 Nov 2019 at 07:29, Kristina Brooks via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > While I understand the difficulty regarding mailing lists especially > if one isn't used to setting up mailboxes and filters to classify and > label emails and do think a web forum may be easier to use, I would > have concerns over Discord. Unlike IRC which has a fairly open
2019 Nov 18
3
RFC: Moving toward Discord and Discourse for LLVM's discussions
On Mon, Nov 18, 2019 at 11:32 AM David Tellenbach via llvm-dev < llvm-dev at lists.llvm.org> wrote: > Hi all, > > +1 from my side for using "faster" or "more direct" communication channels > such > as Discord (no strong opinion on the choice of any particular tool here) > for > informal chats and discussions on a "support level". This is
2019 Nov 19
2
Fwd: RFC: Moving toward Discord and Discourse for LLVM's discussions
On 11/19/19 9:09 AM, Zachary Turner via llvm-dev wrote: Note there is also Slack, which does not have these problems. Not sure why that keeps being overlooked My understanding is this is because Slack does not have good moderation tools. I'm unfamiliar with further details in this regard. -Hal On Tue, Nov 19, 2019 at 7:07 AM Zachary Turner <zturner at roblox.com<mailto:zturner at
2019 Nov 18
5
RFC: Moving toward Discord and Discourse for LLVM's discussions
The lists are working well for the people who are already invested in the community though - as was identified by Chandler they aren't working as well for new people. I'm an insanely confident Scotsman with just about zero fear of any/all social situations, and I've always found this mailing list to be utterly terrifying (thus I've been a 10 year mostly-lurker). My fear
2003 Jan 20
1
curious code mistakes
hi, know anybody why this happen ? I''m using winedt , the old code saved in an .R call syntax error''s. Curious is, when i''m type below the same code , it works ??? ...imho a print type problem, what i''m never before observed and can''t recognize with my eyes ? P.S. R.1.6.1 /w2k thanks for advance & regards,christian >>getfile <-
2019 Nov 19
2
RFC: Moving toward Discord and Discourse for LLVM's discussions
David, I'm glad you mentioned Discord's T&Cs. I'm not generally concerned about these kinds of things, but Discord's seems particularly aggressive. Particularly the phrase "perpetual, nonexclusive, transferable, royalty-free, sublicensable, and worldwide license" is... a lot. Since LLVM is a permissively licensed project I assume many of our contributors care about
2019 Nov 20
3
[cfe-dev] RFC: Moving toward Discord and Discourse for LLVM's discussions
On Wed, Nov 20, 2019 at 12:18 PM Renato Golin <rengolin at gmail.com> wrote: > > On Wed, 20 Nov 2019 at 08:44, Whisperity via llvm-dev > <llvm-dev at lists.llvm.org> wrote: > > There *are* open-source Discord clients, 3rd party tools and the like. > > This is a big uphill fight that is rarelly worthy. Not to mention > privacy guarantees and terms and conditions
2019 Nov 18
6
RFC: Moving toward Discord and Discourse for LLVM's discussions
On Mon, Nov 18, 2019 at 11:55 AM David Chisnall via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > On 18/11/2019 16:39, Stefan Teleman via llvm-dev wrote: > > I can't recall an instance when I had difficulty using, or was > > intimidated by, email, for saying something on a mailing list. > > Subscribing to a mailing list, particularly one as high-traffic as >
2019 Nov 18
2
RFC: Moving toward Discord and Discourse for LLVM's discussions
> > | mailing lists for longer-form discussions are unfamiliar, difficult, > and often intimidating for newcomers > > Um… what? While I know (via my own children) that folks nowadays use > multiple avenues of communication, it’s **really** hard to imagine email > as a **mechanism** being unfamiliar/difficult/intimidating. Moving to a > new mechanism wouldn’t alter the
2004 Mar 22
5
Your email message was blocked
MailMarshal (an automated content monitoring gateway) has not delivered the following message: Message: B0000c89bd.00000001.mml From: samba@samba.org To: lianaj@balgrammar.vic.edu.au Subject: Question This is due to automatic rules that have determined that the intended recipient is not authorized to receive messages with certain potentially dangerous filetypes attached.
2019 Nov 19
3
Fwd: RFC: Moving toward Discord and Discourse for LLVM's discussions
Slack's community moderation features are pretty terrible - it's simply not set up for managing public-facing communities; it's set up for managing private workplace team collaboration.  The best way to try to explain the features which are missing are to look at something like the Matrix moderation guide (https://matrix.org/docs/guides/moderation/); many of these features are