Displaying 6 results from an estimated 6 matches for "emend".
Did you mean:
amend
2020 May 20
1
Re: dsync “destination” argument
...s not support -1 btw.
>
> doveadm backup -u john -R ssh sshuser at remote "sudo /usr/bin/doveadm dsync-server -u john"
Isn?t this actually the same syntax that I?m asking about, where <destination> is a command name and arguments? I guess the documentation is just in want of emendation to mention this usage?
-FG
2020 May 16
2
dsync “destination” argument
Hello,
Some code that I didn?t write but am maintaining passes a local script?s path as dsync?s ?destination? argument, like so:
dsync -D -u john -v backup -R -1 "/code/dsync_client.pl" 127.0.0.1 john at mydomain.org
dsync_client.pl establishes a TCP connection with a remote dsync process then acts as a proxy between the two dsync processes. ?127.0.0.1? and ?john at mydomain.org?
2015 Jun 20
2
Finished a prototype of GSoC project: Implement a new doc toolchain
Hi,
Kunaal and I have completed a prototype of the first part of our GSoC project (implement a new doc toolchain). Our goal is to implement a doc toolchain for short how-to docs and lower the barrier for new comers to contribute.
This is the workflow of the prototype:
1. Contributor creates a new pull request on GitHub
2. A corresponding issue is automatically created on Pagure
3. Staff and
2015 Jul 08
0
Finished a prototype of GSoC project: Implement a new doc toolchain
...ome suggestions about the workflow above and about the toolchain? The original GSoC idea can be found here: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain <http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain>
I like the CI. I'd love to have us consider including something like emender in a future release that could do CI on the PR and post a response with any automated integration failures.
> We use Pagure as a part of the toolchain. Pagure is an excellent git-centered forge created by Pierre-Yves Chibon <pingou at pingoured.fr <mailto:pingou at pingoured.fr>>....
2008 Jul 14
6
"XENBUS: Device with no driver" errors on Debian
I am running debian lenny, with the standard Xen 3.2 packages, with
the 2.6.18-6-xen-686 kernel as dom0, and 2.6.24-1-xen-686 as domU.
Everything is working fine apart from the console and the PCI
passthrough. I am getting these errors in the domU on startup:
XENBUS: Device with no driver: device/pci/0
XENBUS: Device with no driver: device/console/0
Does this mean the modules are missing?
2015 Jul 08
2
Finished a prototype of GSoC project: Implement a new doc toolchain
...review. Could you please give us some suggestions about
> the workflow above and about the toolchain? The original GSoC idea can be
> found here: http://wiki.centos.org/GSoC/2015/Ideas#docs-toolchain
>
>
> I like the CI. I'd love to have us consider including something like
> emender in a future release that could do CI on the PR and post a response
> with any automated integration failures.
>
Thanks! We don't have much knowledge about that, once we get there, maybe
you can help us. I made a sample CI for listening to github repo changes,
and automatically generati...