From: "Jay Soffian" <jaysoffian+git@gmail.com>
To: "Christian Couder" <chriscool@tuxfamily.org>
Cc: "Dmitry Potapov" <dpotapov@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Improve git-help--browse browser support under OS X
Date: Sun, 10 Feb 2008 21:13:47 -0500 [thread overview]
Message-ID: <76718490802101813n5b2121fcp25b4c65eb32ab14e@mail.gmail.com> (raw)
In-Reply-To: <200802101445.16033.chriscool@tuxfamily.org>
On Feb 10, 2008 8:45 AM, Christian Couder <chriscool@tuxfamily.org> wrote:
> I wonder if "open" works on OS X outside the OS X GUI environment. (And do
> people use OS X outside the OS X GUI environment ?)
"open" simulates double-clicking on a document icon, so, no it does
not make sense to use it unless the GUI is active. What I was
referring to though is that you can't ssh into another OS X host and
use open, even if there is a user logged into the GUI on that host,
for obvious security reasons.
> In the git "next" branch, "git-help--browse" has been
> renamed "git-web--browse". And the original patch is
> against "git-web--browse" except in the title where it is
> about "git-help--browse".
Yeah, my typo in the title.
> Anyway now in "next", "git-web--browse" is used by both "git help" and "git
> instaweb", so the documentation of both commands need an update.
The git instaweb documentation update should be in a separate patch.
Though I think maybe the right way to handle this is add a new doc for
git-web--browse and then have the instaweb and help docs refer to
that, no?
BTW, what is the reason for the two-dashes in git-web--browse's name?
j.
next prev parent reply other threads:[~2008-02-11 2:14 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-08 21:23 [PATCH] Improve git-help--browse browser support under OS X jaysoffian+git
2008-02-09 20:20 ` Dmitry Potapov
2008-02-10 2:15 ` Jay Soffian
2008-02-10 12:43 ` Dmitry Potapov
2008-02-10 13:45 ` Christian Couder
2008-02-11 2:13 ` Jay Soffian [this message]
2008-02-11 5:03 ` Christian Couder
2008-02-11 2:10 ` Jay Soffian
2008-02-11 2:24 ` [PATCH] git-web--browse: improve " jaysoffian+git
2008-02-11 3:01 ` Junio C Hamano
2008-02-11 14:15 ` Jay Soffian
2008-02-12 16:40 ` Jay Soffian
2008-02-13 6:55 ` Christian Couder
2008-02-13 22:14 ` Junio C Hamano
2008-02-13 22:46 ` Pieter de Bie
2008-02-14 0:13 ` Jay Soffian
2008-02-14 5:09 ` Christian Couder
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=76718490802101813n5b2121fcp25b4c65eb32ab14e@mail.gmail.com \
--to=jaysoffian+git@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=dpotapov@gmail.com \
--cc=git@vger.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 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).