Displaying 5 results from an estimated 5 matches for "user_docs".
Did you mean:
user_doc
2004 Jul 28
3
only 1.3 of 12 GB will transfer from OSX to Linux
...m an rsync server on Mac OSX to a
Linux machine. I'm doing everything as root on both ends to make sure it's
not a permissions issue, but still can't get all the files to transfer.
I have the rsync server running on OSX as root, like this:
server:/Users root# cat /etc/rsyncd.conf
[user_docs]
path = /Users
read only = true
transfer logging = no
server:/Users root# ps -alx|grep rsync
0 1658 1 0 31 0 18268 372 - Ss ?? 0:00.01
rsync --daemon
On the client, I run this:
[client:/tmp/server/Users]# rsync -av --delete server::user_docs/
/tmp/server/Users/...
2020 Jan 21
2
Phabricator -> GitHub PRs?
Hi folks,
Another thought on the topic is tooling support and tool integration:
There is a hughe ecosystem around Github and very little around Phabricator.
It took me 2 days to set up build jobs for the 10.x release branch [1].
There are nice build integrations for Github and it was smooth sailing.
Setting up a build job for pull requests would just be a few clicks now.
In contrast I've
2019 Dec 12
4
RFC: Using GitHub Actions for CI testing on the release/* branches
Please forgive the incorrect threading on this reply to Tom Stellard's RFC.
> I would like to start using GitHub Actions[1] for CI testing on the
release/*
> branches. As far as I know we don't have any buildbots listening to the
> release branches, and I think GitHub Actions are a good way for us to
> quickly bring-up some CI jobs there.
Personally, I feel that Tom's
2019 Dec 13
2
RFC: Using GitHub Actions for CI testing on the release/* branches
> I think my concern is that LLVM could prove to be too big and require too
many resources for github's infrastructure. How many patches go into LLVM a
day, and how many build and test jobs does GitHub allow users to run
concurrently before being throttled?
Please, no one confuse "what should be LLVM's official CIs" with "what can
we do to make it easier for individuals
2020 Feb 06
2
RFC: Using GitHub Actions for CI testing on the release/* branches
On 02/06/2020 08:41 AM, Russell Gallop wrote:
> Hi Tom,
>
> Thank you for setting this up. It's very useful.
>
> One question about what this builds. It only builds "ninja check-all", not "ninja all"[1]. check-all isn't a strict superset of all so while this covers most things, this does miss building a few things such as:
> bin/clang-offload-wrapper