From: Christian Couder <chriscool@tuxfamily.org>
To: Petr Baudis <pasky@suse.cz>
Cc: Ramsay Jones <ramsay@ramsay1.demon.co.uk>,
Junio C Hamano <gitster@pobox.com>,
GIT Mailing-list <git@vger.kernel.org>
Subject: Re: [RFC/PATCH] git-web--browse: don't add start as candidate on Ubuntu
Date: Sun, 4 Jan 2009 08:33:25 +0100 [thread overview]
Message-ID: <200901040833.25849.chriscool@tuxfamily.org> (raw)
In-Reply-To: <495D3964.6040006@ramsay1.demon.co.uk>
Le jeudi 1 janvier 2009, Ramsay Jones a écrit :
> Signed-off-by: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
> ---
>
> Hi *,
>
> When upgrading to v1.6.1, I noticed that the html help had stopped
> working on Linux (Ububtu), viz:
>
> $ git help -w tag
> start: Need to be root
>
> So, after squinting at git-web--browse.sh, I tried a few things:
>
> $ ls /bin/start
> ls: /bin/start: No such file or directory
> $ test -n /bin/start; echo $?
> 0
> $ which start
> /sbin/start
> $ start fred
> start: Need to be root
> $ ls -l /sbin/start
> lrwxrwxrwx 1 root root 7 2007-06-24 19:45 /sbin/start -> initctl*
>
> So, it would seem that /sbin/start is part of upstart, which would
> explain the "Need to be root" ;-)
>
> $ test -x /bin/start; echo $?
> 1
> $
>
> So, the patch below fixes the issue for me, but as I don't have MinGW
> installed, I can't test this fix works there.
>
> Does anybody else see this issue and can someone test the patch?
Petr, as you added support for using /bin/start on MinGW, could you test?
Thanks,
Christian.
next prev parent reply other threads:[~2009-01-04 7:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-01 21:45 [RFC/PATCH] git-web--browse: don't add start as candidate on Ubuntu Ramsay Jones
2009-01-04 7:33 ` Christian Couder [this message]
2009-01-04 7:53 ` Junio C Hamano
2009-01-04 13:29 ` Petr Baudis
2009-01-12 21:05 ` [PATCH v2] " Ramsay Jones
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=200901040833.25849.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=pasky@suse.cz \
--cc=ramsay@ramsay1.demon.co.uk \
/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;
as well as URLs for NNTP newsgroup(s).