All of lore.kernel.org
 help / color / mirror / Atom feed
From: Hans Deragon <hans@deragon.biz>
To: autofs@linux.kernel.org
Subject: backfstype patch.
Date: Fri, 16 Jul 2004 14:45:28 -0400	[thread overview]
Message-ID: <40F82248.2050803@deragon.biz> (raw)

Greetings.


   Remember me with my backfstype patch?  Some people commented on it, I replied 
and then never got any answers since.  Altough functional, my patch was 
questionned; the fix was not at the right place within the code (from a 
design/elegance point of view; technically it works great).  As I explained, I 
have no knowledge of the overall architecture of Autofs and unfortunatly, I do 
not have the time to get deep into it.

   Can my patch still be applied in the main branch until it is moved into a 
more appropriate area of the code?  Its still adds the new backsftype support, 
does not cause any problems, is very localized, and very usefull.  I have been 
running it since the last 2 weeks without any problems.  I am rolling it out in 
the production environment.


Best regards,
Hans Deragon
--
Consultant en informatique/Software Consultant
Deragon Informatique inc.     Open source:
http://www.deragon.biz        http://facil.qc.ca (Promotion du libre)
mailto://hans@deragon.biz     http://autopoweroff.sourceforge.net (Logiciel)

             reply	other threads:[~2004-07-16 18:45 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-07-16 18:45 Hans Deragon [this message]
2004-07-16 19:01 ` backfstype patch Jeff Moyer
2005-03-02 21:03   ` Greg Bradner
2005-03-03  2:15     ` Ian Kent
2004-07-17  4:16 ` raven
  -- strict thread matches above, loose matches on Subject: below --
2004-06-29 20:10 Hans Deragon
2004-06-30 13:26 ` Jeff Moyer
2004-06-30 14:00   ` raven
2004-06-30 15:01   ` Hans Deragon
2004-06-30 13:31 ` Mike Waychison
2004-06-30 13:51   ` Jeff Moyer
2004-06-30 14:20     ` Mike Waychison
2004-06-30 14:22       ` Jeff Moyer
2004-06-30 15:11       ` Hans Deragon
2004-06-30 14:28     ` Mike Waychison

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=40F82248.2050803@deragon.biz \
    --to=hans@deragon.biz \
    --cc=autofs@linux.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.