git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marco Costalba <mcostalba@gmail.com>
To: Jan Hudec <bulb@ucw.cz>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Common library for Git GUIs
Date: Wed, 18 Feb 2009 09:04:47 +0100	[thread overview]
Message-ID: <e5bfff550902180004x5e10e391wb80988fa892da413@mail.gmail.com> (raw)
In-Reply-To: <20090217192825.GA2216@efreet.light.src>

On Tue, Feb 17, 2009 at 20:28, Jan Hudec <bulb@ucw.cz> wrote:
>
> Often I need to configure some options in ~/.gitconfig and .git/config, but
> the GUIs generally only allow to set very few basic ones. I had to resort to
> editing ~/.gitconfig to turn off the cursed core.autocrlf, because git gui
> does not have that setting. And there are many more settings like that that
> users may want to tweak and something to guide them would be highly
> appreciated especially by the command-line-fearing windooze users.
>
> So my idea is to provide some kind of "property sheet" -- a treeview with all
> the sections and options with editable values with proper constraints (so
> boolean and enum values could be entered with drop-down menus) and
> descriptions.


This is nice. Thanks for the idea, I will implement that in qgit when
I find a bit of time :-)



Regarding your proposal I really wish you good luck and especially "have fun!!!"

For me it is like to trash out 95% of the stuff and start again from
zero because of the last 5% is missing (but I can add it anyway with
much smaller effort and time spent).

I understand the main reason, as per any GPL project, is having fun
and good time coding and exchanging ideas with peers, but I really
lack time and I am now moving to different interests. So, thank you
very much, but I think I'll stick with qgit.

Best
Marco

  reply	other threads:[~2009-02-18  8:06 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16 21:24 [RFC] Common library for Git GUIs Jan Hudec
2009-02-17 12:55 ` Guilhem Bonnefille
2009-02-17 20:39   ` Jan Hudec
     [not found] ` <e5bfff550902162337m43156398kb06320796838c953@mail.gmail.com>
2009-02-17  7:40   ` Fwd: " Marco Costalba
2009-02-17 19:28   ` Jan Hudec
2009-02-18  8:04     ` Marco Costalba [this message]
2009-02-19  7:30       ` David Aguilar
2009-02-17 20:08 ` Pieter de Bie
2009-02-17 21:21   ` Jan Hudec
2009-02-17 23:45     ` Johannes Schindelin
2009-02-18  5:52       ` Jan Hudec
2009-02-18  1:38     ` Frank Li
2009-02-18  5:57       ` Jan Hudec
2009-02-18  6:02         ` Abhijit Bhopatkar
2009-02-18  5:56 ` Abhijit Bhopatkar

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=e5bfff550902180004x5e10e391wb80988fa892da413@mail.gmail.com \
    --to=mcostalba@gmail.com \
    --cc=bulb@ucw.cz \
    --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).