All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>,
	Junio C Hamano <gitster@pobox.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 04:21:35 -0800 (PST)	[thread overview]
Message-ID: <m3d4tmveep.fsf@roke.D-201> (raw)
In-Reply-To: <404A9328-65CF-479E-A109-0C8B09CA43D5@wincent.com>

Wincent Colaiuta <win@wincent.com> writes:

> El 4/12/2007, a las 12:48, Johannes Schindelin escribió:
> 
> > You know, without patches you will not convince me ;-)
> 
> A number of patches have already been submitted (by Nguy…n Tha  
> Ngc Duy, I believe); you know, the "Move all dashed form git  
> commands to libexecdir" thread and its precursors. I was just arguing  
> in support of the rationale behind them.

I think creating separate libexecdir, and moving there _helpers_ first
(i.e. command which are neither plumbing, nor porcelain, but are
meant to be called _only_ by other commands) would be a good idea,
perhaps even pre 1.5.4.

By the way, if (when) dashed form of commands would get moved to
libexecdir, the INSTALL fragment below talking about removin wrapper
script would have to be changed. But does anyone use GNU Interactive
Tools anymore (IIRC the package name was changed to gitfm or sth.)

<quote src="INSTALL">
 - git normally installs a helper script wrapper called "git", which
   conflicts with a similarly named "GNU interactive tools" program.

   Tough.  Either don't use the wrapper script, or delete the old GNU
   interactive tools.  None of the core git stuff needs the wrapper,
   it's just a convenient shorthand and while it is documented in some
   places, you can always replace "git commit" with "git-commit"
   instead.

   But let's face it, most of us don't have GNU interactive tools, and
   even if we had it, we wouldn't know what it does.  I don't think it
   has been actively developed since 1997, and people have moved over to
   graphical file managers.
</quote>

-- 
Jakub Narebski

  reply	other threads:[~2007-12-04 12:22 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 [this message]
2007-12-04 17:45           ` Junio C Hamano

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=m3d4tmveep.fsf@roke.D-201 \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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.