Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Baruch Siach <baruch@tkos.co.il>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] autofs: new package
Date: Mon, 23 Nov 2015 08:27:11 +0200	[thread overview]
Message-ID: <20151123062711.GI2177@tarshish> (raw)
In-Reply-To: <alpine.DEB.2.11.1511230758100.26339@tanhuma.tkos.co.il>

Hi Yonatan,

On Mon, Nov 23, 2015 at 08:00:32AM +0200, Jonathan Ben Avraham wrote:
> On Mon, 23 Nov 2015, Baruch Siach wrote:
> >On Sun, Nov 22, 2015 at 03:48:20PM +0200, Jonathan Ben-Avraham wrote:
> >>+config BR2_PACKAGE_AUTOFS
> >>+	bool "autofs"
> >>+	select BR2_PACKAGE_NFS_UTILS # runtime
> >>+	select BR2_PACKAGE_RPCBIND # runtime
> >>+	depends on BR2_TOOLCHAIN_HAS_THREADS # rpcbind
> >>+	depends on BR2_USE_MMU # nfs-utils, rpcbind
> >>+	help
> >>+	  Based on the Debian autofs package description:
> >>+	  Autofs controls the operation of the automount daemons. The automount
> >>+	  daemons automatically mount filesystems when they are used and unmount
> >>+	  them after a period of inactivity based on a set of pre-configured
> >>+	  maps defined by default in /etc/auto.master. The kernel automounter
> >>+	  implements SunOS style automounter under Linux and requires a kernel
> >>+	  version of at least 2.6.17 and the autofs4 kernel module.
> >>+
> >>+	  git://git.kernel.org/pub/scm/linux/storage/autofs/autofs.git
> >
> >The browser friendly link
> >https://git.kernel.org/cgit/linux/storage/autofs/autofs.git/ would be better
> >here, I believe.
> 
> Why? I always struggle to convert back from the browser URLs to plain git
> URL's so that I can see the sources in vi on my machine and index them. Why
> would anyone want to use an HTML browser to do this? Doesn't make sense.

Well, we usually put a link to the project homepage. In the absence of a 
suitable homepage, we use a git repo link. You can find a git/vi friendly link 
if you scroll down the git repo summary page. Converting the other way seems 
to me quite a bit harder for the less git/vi literate.

baruch

-- 
     http://baruch.siach.name/blog/                  ~. .~   Tk Open Systems
=}------------------------------------------------ooO--U--Ooo------------{=
   - baruch at tkos.co.il - tel: +972.2.679.5364, http://www.tkos.co.il -

  reply	other threads:[~2015-11-23  6:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22 13:48 [Buildroot] [PATCH 1/1] autofs: new package Jonathan Ben-Avraham
2015-11-23  5:41 ` Baruch Siach
2015-11-23  6:00   ` Jonathan Ben Avraham
2015-11-23  6:27     ` Baruch Siach [this message]
     [not found]       ` <alpine.DEB.2.11.1511230845330.26339@tanhuma.tkos.co.il>
     [not found]         ` <20151123071348.GL2177@tarshish>
2015-11-23  7:22           ` Jonathan Ben Avraham
2015-11-30 21:26 ` Thomas Petazzoni

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=20151123062711.GI2177@tarshish \
    --to=baruch@tkos.co.il \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox