From: Junio C Hamano <junkio@cox.net>
To: "Theodore Ts'o" <tytso@mit.edu>
Cc: git@vger.kernel.org
Subject: Re: Questions about git-rev-parse
Date: Tue, 27 Feb 2007 18:40:47 -0800 [thread overview]
Message-ID: <7vvehn2eds.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <E1HMETh-0004BO-Lw@candygram.thunk.org> (Theodore Ts'o's message of "Tue, 27 Feb 2007 21:23:37 -0500")
"Theodore Ts'o" <tytso@mit.edu> writes:
> So I'm wondering if I'm missing something about historical context,
> since from looking at git-rev-parse, it looks like not a lot of thought
> went into its design, and it has a bunch of stuff that grew via
> accretion; or maybe I'm not understanding why it was designed the way it
> was?
You are lacking historical context that our porcelain-ish were
all Bourne shell scripts. If you check out an old version (say
v0.99), it would be apparent why translating symbolic names to
object names and canonicalizing a..b to b ^a were useful to help
them.
These days, "log" family got sufficiently smart that there are
not many reasons to write shell pipeline that has rev-list on
the upstream with diff-tree --stdin on the downstream anymore,
and rev-parse outlived its original purpose of sifting between
rev-list args/flags and others.
next prev parent reply other threads:[~2007-02-28 2:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-28 2:23 Questions about git-rev-parse Theodore Ts'o
2007-02-28 2:40 ` Junio C Hamano [this message]
2007-02-28 2:52 ` Theodore Tso
2007-02-28 3:33 ` Linus Torvalds
2007-02-28 6:40 ` Theodore Tso
2007-02-28 8:54 ` Andy Parkins
2007-02-28 16:00 ` Linus Torvalds
2007-02-28 3:19 ` Linus Torvalds
2007-03-01 2:16 ` Willhelm Busch
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=7vvehn2eds.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=git@vger.kernel.org \
--cc=tytso@mit.edu \
/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.