git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: John Tapsell <johnflux@gmail.com>
Cc: git@vger.kernel.org,
	Johannes Schindelin <johannes.schindelin@gmx.de>,
	andre.harms@kuhlsolutions.de, Matthieu Moy <Matthieu.Moy@imag.fr>
Subject: Re: Modern Git GUI
Date: Tue, 26 Jan 2010 12:35:57 +0100	[thread overview]
Message-ID: <4B5ED39D.1020804@drmicha.warpmail.net> (raw)
In-Reply-To: <43d8ce651001250630p51761f6eyce8b89da6ffcd7b@mail.gmail.com>

[Re-adding cc culled by John. Bad boy :) ]
John Tapsell venit, vidit, dixit 25.01.2010 15:30:
> 2010/1/25 Johannes Schindelin <Johannes.Schindelin@gmx.de>:
>> Hi,
>>
>> On Sun, 24 Jan 2010, Matthieu Moy wrote:
>>
>>> If you decide to go on with your project, either you want to carry it
>>> out alone, or you'll have to convince other developers to join. In the
>>> second case, a good starting point would be to explain why the other GUI
>>> are not good enough, and why you can't just contribute to them.
>>
>> Actually, a much better way would be to be positive, not negative.  I.e.
>> to show something you did, which hopefully entices others to use your
>> project (and maybe contribute to it).
> 
> Actually in this case, I don't think that would be good enough.  My
> first thought would be "why didn't he just add this feature to an
> existing GUI rather than reinventing the wheel yet again".  So there
> would really have to be good reasons why the other GUIs aren't a good
> enough starting point

A first step may be making the feature matrix in the wiki more honest -
I've been meaning to do this for ages... For example, a gui which simply
calls "gitk" for history view simply does not support history view
according to my books, at least not on the same level (gui
*integration*) as guis doing this natively. Or else gitk would have all
git-gui features and vice versa... or even plain git, for that matter.

Michael

  reply	other threads:[~2010-01-26 11:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-01-23 21:40 Modern Git GUI André Harms
2010-01-24  9:50 ` Matthieu Moy
2010-01-24 20:43   ` André Harms
2010-01-25 14:25   ` Johannes Schindelin
2010-01-25 14:30     ` John Tapsell
2010-01-26 11:35       ` Michael J Gruber [this message]
2010-01-26 22:39 ` Guilhem Bonnefille
2010-01-28 15:11 ` Maxime Lévesque

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=4B5ED39D.1020804@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=Matthieu.Moy@imag.fr \
    --cc=andre.harms@kuhlsolutions.de \
    --cc=git@vger.kernel.org \
    --cc=johannes.schindelin@gmx.de \
    --cc=johnflux@gmail.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 NNTP newsgroup(s).