From: Theodore Tso <tytso@mit.edu>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: James Bowes <jbowes@dangerouslyinc.com>, git@vger.kernel.org
Subject: Re: [PATCH 0/2] Make gc a builtin.
Date: Mon, 12 Mar 2007 09:36:12 -0400 [thread overview]
Message-ID: <20070312133612.GD4372@thunk.org> (raw)
In-Reply-To: <Pine.LNX.4.63.0703121222350.22628@wbgn013.biozentrum.uni-wuerzburg.de>
On Mon, Mar 12, 2007 at 12:23:41PM +0100, Johannes Schindelin wrote:
> Hi,
>
> On Sun, 11 Mar 2007, Theodore Tso wrote:
>
> > On Sun, Mar 11, 2007 at 06:06:56PM -0400, James Bowes wrote:
> > > The following two patches make git-gc a builtin command.
> >
> > What's the advantage in making git-gc a builtin command?
>
> Portability. Plus, James wanted to get involved in Git development, and
> building in gc really was the shortest path into that.
>
I'm not sure I understand the portability argument? All of the
platforms that git currently supports will handle shell scripts,
right?
Heck, git-commit is still a shell script, and that's a rather, ah,
fundamental command, isn't it?
- Ted
next prev parent reply other threads:[~2007-03-12 13:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-11 22:06 [PATCH 0/2] Make gc a builtin James Bowes
2007-03-11 22:06 ` [PATCH 1/2] run-command: Make run_command_va_opt public and add run_command_va James Bowes
2007-03-11 22:06 ` [PATCH 2/2] Make gc a builtin James Bowes
2007-03-11 22:48 ` Johannes Schindelin
2007-03-12 2:11 ` Junio C Hamano
2007-03-12 2:51 ` [PATCH] " James Bowes
2007-03-12 14:43 ` Shawn O. Pearce
2007-03-12 3:07 ` [PATCH 2/2] " Johannes Schindelin
2007-03-12 2:57 ` [PATCH 0/2] " Theodore Tso
2007-03-12 11:23 ` Johannes Schindelin
2007-03-12 13:36 ` Theodore Tso [this message]
2007-03-12 19:14 ` Linus Torvalds
2007-03-13 0:48 ` Jakub Narebski
2007-03-13 1:20 ` Linus Torvalds
2007-03-12 14:29 ` Shawn O. Pearce
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=20070312133612.GD4372@thunk.org \
--to=tytso@mit.edu \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=jbowes@dangerouslyinc.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).