From: "Mike Coleman" <tutufan@gmail.com>
To: git@vger.kernel.org
Subject: suggested feature: someone mails me a blob, git please tell me what it is
Date: Fri, 16 Feb 2007 10:23:40 -0600 [thread overview]
Message-ID: <3c6c07c20702160823j316c52f4pe4cf5ca8a882e194@mail.gmail.com> (raw)
Here's a suggestion for a git feature, if git doesn't already have it.
Since git generally doesn't use RCS-style keyword cookies (like
"$Id$"), it'd be nice to have some other way to identify an installed
file. Perhaps you'd want to know exactly what rev a user is running,
for example.
It seems like it should be fairly easy, given a blob (the file), for
git to describe what it knows about it. For example, it could provide
a list of commits that it's a part of, etc. It'd be *really* nice if
only the output of the sha1sum command on the blob were needed. (I
can't recall exactly how git's blob SHA1's are computed--maybe this
isn't feasible.)
Mike
next reply other threads:[~2007-02-16 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-16 16:23 Mike Coleman [this message]
2007-02-16 16:48 ` suggested feature: someone mails me a blob, git please tell me what it is Nicolas Pitre
2007-02-16 17:14 ` Matthieu Moy
2007-02-16 17:37 ` Linus Torvalds
2007-02-17 6:10 ` Shawn O. Pearce
2007-02-17 21:40 ` Andy Parkins
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=3c6c07c20702160823j316c52f4pe4cf5ca8a882e194@mail.gmail.com \
--to=tutufan@gmail.com \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).