From: Junio C Hamano <gitster@pobox.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Wincent Colaiuta <win@wincent.com>,
Reid Barton <rwbarton@MIT.EDU>,
git@vger.kernel.org
Subject: Re: git-add--interactive works only in top level
Date: Tue, 04 Dec 2007 09:45:13 -0800 [thread overview]
Message-ID: <7vd4tm5p7a.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0712041148310.27959@racer.site> (Johannes Schindelin's message of "Tue, 4 Dec 2007 11:48:57 +0000 (GMT)")
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
>> Here he have two options: blame the user for his/her stupidity, or look
>> at this a UI problem and try to make the UI "idiot proof".
>>
>> In this particular case I see no impediment to favouring the second
>> option, because we're not talking about making changes that would make
>> Git less powerful or useful for "non-idiots", "power users" or "real
>> men" (whatever you want to call them). In other words, we are not
>> talking about "dumbing down" Git for the sake of the ignorant. This is
>> an opportunity to polish the UI in the same way that we polish the
>> internal pack format.
>
> You know, without patches you will not convince me ;-)
Honestly, I do not want a patch for that to git-add--interactive.
Once WIncent's and Dan's UI enhancements to it becomes stable (not
implementation-wise but more interface- and user-experience-wise),
rewriting it in C should not be too much of a hassle. When that
happens, it won't be a standalone program but will be a function
builtin-add.c::interactive_add() will call into and we won't have this
problem at that point. If somebody does do a patch, the time is better
spent there instead.
prev parent reply other threads:[~2007-12-04 17:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-04 3:19 git-add--interactive works only in top level Reid Barton
2007-12-04 5:44 ` Junio C Hamano
2007-12-04 6:07 ` Reid Barton
2007-12-04 6:22 ` Junio C Hamano
2007-12-04 10:37 ` Wincent Colaiuta
2007-12-04 11:48 ` Johannes Schindelin
2007-12-04 11:56 ` Wincent Colaiuta
2007-12-04 12:21 ` Jakub Narebski
2007-12-04 17:45 ` Junio C Hamano [this message]
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=7vd4tm5p7a.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=rwbarton@MIT.EDU \
--cc=win@wincent.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.