Thanks for the heads up :) If Julien does not notice my email in a couple of days I'll resubmit with the catchy [PATCH] tag you suggested.
Also in case this should be the norm for submitting patches I attach a patch to PATCH to add [PATCH] in the subject (if your head hurts after reading the sentence, observe that this is intended). Best, Alex On Tue, Mar 17, 2009 at 8:01 PM, Andrei Thorp <[email protected]> wrote: > Nifty. As a slight suggestion, putting [PATCH] in your topic is the > conventional way to get your patches noticed, in my understanding. > > Cheers, and thanks for your work. > > -Andrei "Garoth" Thorp > > On Tue, Mar 17, 2009 at 4:00 PM, Alex Cornejo <[email protected]> wrote: > > Hi ppl, > > > > A lot of universities (and corporations) use kerberos for authentication > and > > OpenAFS to host the folders. However, it is not possible to create > sockets > > on OpenAFS (this is probably true for other remote/distributed file > > systems). > > > > Currently awesome reports its unable to bind a socket (with permission > > denied) and continues normaly. However this means the user is unable to > > control awesome using awesome-client or similar. > > > > A simple workaround for this is to fall back to /tmp/.awesome-ctl before > > giving up after ~/.awesome-ctl failed. The following patch does precisly > > this, it works perfectly on my desktop (on openafs) and my laptop > (regular > > ext3). > > > > PS: As a bonus I attached a path to merge two loops in the keybinding > > section of aweseomerc.lua into 1, I see no reason to spam the list again > for > > such a small patch. > > > > Cheers, > > > > Alex >
From caa3e1a31a7825623b85deeda13c4360d3253e9c Mon Sep 17 00:00:00 2001 From: Alex Cornejo <[email protected]> Date: Tue, 17 Mar 2009 20:11:31 -0400 Subject: [PATCH] Added [PATCH] subject suggestion. Signed-off-by: Alex Cornejo <[email protected]> --- PATCHES | 1 + 1 files changed, 1 insertions(+), 0 deletions(-) diff --git a/PATCHES b/PATCHES index cc050de..6abb0e5 100644 --- a/PATCHES +++ b/PATCHES @@ -23,3 +23,4 @@ If you plan to submit patches, here's a checklist: - send the patch to the list ([email protected]) if (and only if) the patch is ready for inclusion. If you use git-send-email(1), please test it first by sending email to yourself. +- use [PATCH] as the prefix in the email subject so it gets noticed. -- 1.5.6.3
