From: Junio C Hamano <junkio@cox.net>
To: Linus Torvalds <torvalds@osdl.org>
Cc: git@vger.kernel.org
Subject: Re: Make "git rev-list" be a builtin
Date: Thu, 18 May 2006 14:50:11 -0700 [thread overview]
Message-ID: <7vejyrngto.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.64.0605181415090.10823@g5.osdl.org> (Linus Torvalds's message of "Thu, 18 May 2006 14:19:20 -0700 (PDT)")
Linus Torvalds <torvalds@osdl.org> writes:
> This was surprisingly easy. The diff is truly minimal: rename "main()" to
> "cmd_rev_list()" in rev-list.c, and rename the whole file to reflect its
> new built-in status.
>
> We should have done this long ago.
Should we have?
Certainly it is almost trivial, and it means we need to worry
about one less file, but is that the point?
next prev parent reply other threads:[~2006-05-18 21:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-18 21:19 Make "git rev-list" be a builtin Linus Torvalds
2006-05-18 21:50 ` Junio C Hamano [this message]
2006-05-18 22:00 ` Linus Torvalds
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=7vejyrngto.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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