search for: feedbacks

On Wed, Aug 02, 2017 at 02:04:54PM +0200, hw wrote: > Just wait and see how he will like the feedback he?s getting here ... Trolling aside (fascist? really?), I've gotten valuable feedback from several people which I really appreciate. I intend to continue to engage with the CentOS community, because when we work on big changes in Fedora which may come to our downstream distributions,

I have a simple feedback form handled by feedback_controller. For methods I use "new" for the form and "create" to handle the feedback submitted. Routes are simple enough: map.resources :feedback What''s odd is this works fine in Rails 1.2.1: <% form_tag(feedback_path) do -%> But in Rails 1.2.2 and 1.2.3 I get: feedback_url failed to generate from

------------------------------------------------------------------------- (deutsche Version unten) Dear SuSE Linux User, thank you for your message regarding "Unknown Exception (feedback@suse.de)". Please note that the email address you sent your message to (feedback@suse.de) is no longer in use. Of course you still can send us your ideas, comments and bug reports related to our

Hello, I have an issue I am having trouble figuring out. I have a Rails app running through lighttpd which is accessed through an Apache proxy. My apache config: <location /rails/> ProxyPass http://localhost:81/ ProxyPassReverse http://localhost:81/ </location> RewriteEngine On RewriteRule ^/rails/(.*) http://localhost:81/$1 [P] So when apache sees /rails/ it

> On Jul 28, 2017, at 1:56 PM, hw <hw at gc-24.de> wrote: > >> Many bugs are fixed in Fedora. Many more bugs are fixed in the >> upstreams. Please remember that Fedora is primarily an *integration* >> project, and the best way to get bugs fixed is for the developers of >> the code in question to be involved. Many Fedora maintainers help >> facilitate this

Feedback Computing 2014 Call for Papers June 17th, 2014, Philadelphia, PA, collocating with USENIX ATC and ICAC http://www.usenix.org/conference/feedbackcomputing14 Submission deadline in two weeks! Key Dates: * Paper submissions due: March 25, 2014, 11:59 p.m. PDT * Notification to authors: April 22, 2014 * Final paper files due: May 22, 2014 Overview: The 2014 International Workshop on

I'm currently using the standard Samba 4.5.8 on Debian 9.1, but would like to have spotlight support for Mac users. As far as I can tell, the standard package isn't compiled with spotlight support, so I will need to compile it myself. Is there an easy way to know what the configure string was that was used to compile the packaged version? I simply want to add the --enable-spotlight flag

Feedback Computing 2014 Call for Papers June 17th, 2014, Philadelphia, PA, collocating with USENIX ATC and ICAC http://www.usenix.org/conference/feedbackcomputing14 Submission deadline in two weeks! Key Dates: * Paper submissions due: March 25, 2014, 11:59 p.m. PDT * Notification to authors: April 22, 2014 * Final paper files due: May 22, 2014 Overview: The 2014 International Workshop on

We'll definitely look into upgrading this, but it's a older, legacy system so we need to see what we can do without breaking it. Returning to the re-adding question, what steps do I need to do to clear the config of the failed peers? Do I just wipe the data directory of the volume, or do I need to clear some other config file/folders as well? Tom Op ma 17 jul. 2017 om 16:39 schreef

We (the Math department at the U of Wisconsin) recently switched over from another server to dovecot One thing that a lot of people here do is set up an on-line form that sends them email. They use formmail for this. I have them edit their procmail config so that all the messages go into a particular mail folder.... So far so good. With our old system, all messages in a folder were kept in a

We had some issues with a volume. The volume is a 3 replica volume with 3 gluster 3.5.7 peers. We are now in a situation where only 1 of the 3 nodes is operational. If we restart the node on one of the other nodes, the entire volume becomes unresponsive. After a lot of trial and error, we have come to the conclusion that we do not wan't to try to rejoin the other 2 nodes in the current form.

CALL FOR PAPERS Feedback Computing 2013 - The 8th International Workshop on Feedback Computing San Jose, California, USA, 25 June 2013 Co-hosted with the 2013 USENIX Federated Conferences Week https://www.usenix.org/conference/feedback13 ----------------------------------------------------------------- IMPORTANT DATES Paper submissions due: March 29, 2013, 11:59 p.m. PDT Notification to

CALL FOR PAPERS Feedback Computing 2013 - The 8th International Workshop on Feedback Computing San Jose, California, USA, 25 June 2013 Co-hosted with the 2013 USENIX Federated Conferences Week https://www.usenix.org/conference/feedback13 ----------------------------------------------------------------- IMPORTANT DATES Paper submissions due: March 29, 2013, 11:59 p.m. PDT Notification to

Jonathan Billings wrote: > >> On Jul 28, 2017, at 1:56 PM, hw <hw at gc-24.de> wrote: >> >>> Many bugs are fixed in Fedora. Many more bugs are fixed in the >>> upstreams. Please remember that Fedora is primarily an *integration* >>> project, and the best way to get bugs fixed is for the developers of >>> the code in question to be involved.

Hi all, Thank you for everyone that participated in the first round of the discussion <http://lists.llvm.org/pipermail/llvm-dev/2020-January/138267.html>. I’ve incorporated feedback into the draft of the proposal, and I’d appreciate it if you could take another look and share your thoughts. One piece of feedback is that GitHub gists aren’t great for detailed feedback and iteration, so I

On Wed, 2 Aug 2017, hw wrote: > That?s what I thought, and it may still be true. Unfortunately, feedback, > bug reports and even fixes and improvements experience so much unkindness > or ignorance in their reception that I?m better off finding a different > solution or fixing the bug myself, with very few exceptions. > > IIRC, Matthew who started this thread gave an overly

The flags -fprofile-generate and -fprofile-use are currently ignored for GCC compatibility. I would like to enable them and give them similar semantics to GCC. These flags are baked pretty deeply into our build environment, so supporting them at the driver level will make our lives a lot simpler. >From https://gcc.gnu.org/onlinedocs/gcc/Optimize-Options.html:

That's the way. However I'd like to highlight that you're running a very old gluster release. We are currently with 3.11 release which is STM and the long term support is with 3.10. You should consider to upgrade to atleast 3.10. On Mon, Jul 17, 2017 at 3:25 PM, Tom Cannaerts - INTRACTO < tom.cannaerts at intracto.com> wrote: > We had some issues with a volume. The volume is

Hi All, I've been going through the bug queue and there's a number that have been waiting for reporter feedback for a long time (in one case 7+ months). Would anyone consider it unduly harsh if I took an axe to the queue and closed any bugs (ie the unconfirmed or WORKSFORME type) that have been waiting for reporter feedback for more than, say, 3 months? (Unless there's a documented

...and virtnet_close. Use enable helper function in virtnet_open. Fixes: 754b8a21a96d ("virtio_net: setup xdp_rxq_info") Signed-off-by: Feng Liu <feliu at nvidia.com> Reviewed-by: Jiri Pirko <jiri at nvidia.com> Reviewed-by: William Tu <witu at nvidia.com> --- v5 -> v6 feedbacks from Xuan Zhuo - add disable_delayed_refill and cancel_delayed_work_sync v4 -> v5 feedbacks from Michael S. Tsirkin - rename helper as virtnet_disable_queue_pair - rename helper as virtnet_enable_queue_pair v3 -> v4 feedbacks from Jiri Pirko - Add symmetric helper function virtnet_enable_qp...