public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Larry Hall (Cygwin)" <reply-to-list-only-lh@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: gitk fails to start after updating cygwin
Date: Fri, 24 Feb 2012 22:54:00 -0000	[thread overview]
Message-ID: <4F4814F0.3090006@cygwin.com> (raw)
In-Reply-To: <70952A932255A2489522275A628B97C31294ECBF@xmb-sjc-233.amer.cisco.com>

On 2/24/2012 5:43 PM, Matt Seitz (matseitz) wrote:
> "Larry Hall (Cygwin)" wrote:
>>
>> Nobody that doesn't need or want it has to install the X-Server.  If
>> one uses gitk though, one has now moved into the category of
> "need/want
>> the X-Server" if one wasn't already in that category. ;-)
>
> Well, they certainly will need/want AN X-Server.  But I thought
> Corrina's point was that in some cases that X-Server does not have to be
> the Cygwin xorg-server (could be a different local X-Server, or even a
> remote X-Server).

True enough, though I expect for most Cygwin users, this is the exception
and not the rule.

> My question is:  are there enough gitk users who would need/want the
> Cygwin xorg-server that it would be worth installing xorg-server by
> default when installing gitk, even though some gitk users may not
> actually need the Cygwin xorg-server?

I would be for adding Cygiwn's xorg-server as a dependency for any
package that needs an X-Server to be generally useful.

-- 
Larry

_____________________________________________________________________

A: Yes.
 > Q: Are you sure?
 >> A: Because it reverses the logical flow of conversation.
 >>> Q: Why is top posting annoying in email?

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

  reply	other threads:[~2012-02-24 22:54 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-24 22:43 Matt Seitz (matseitz)
2012-02-24 22:54 ` Larry Hall (Cygwin) [this message]
2012-02-24 23:38   ` Mike Kaganski
2012-02-25  4:42     ` Larry Hall (Cygwin)
2012-02-26  4:36 ` Yaakov (Cygwin/X)
  -- strict thread matches above, loose matches on Subject: below --
2012-02-27 19:35 Matt Seitz (matseitz)
2012-02-24 20:50 Matt Seitz (matseitz)
2012-02-24 22:16 ` Larry Hall (Cygwin)
2012-02-24 19:26 Matt Seitz (matseitz)
2012-02-24 20:09 ` Corinna Vinschen
2012-02-10 23:41 Matt Seitz (matseitz)
2012-02-10 23:02 Arnon Moscona
2012-02-11  5:40 ` marco atzeri
2012-02-17 22:34   ` Bill Hoffman
2012-02-17 22:55     ` marco atzeri
2012-02-21  2:32       ` Yaakov (Cygwin/X)
2012-02-20  8:34     ` Csaba Raduly

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=4F4814F0.3090006@cygwin.com \
    --to=reply-to-list-only-lh@cygwin.com \
    --cc=cygwin@cygwin.com \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).