git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: merlyn@stonehenge.com (Randal L. Schwartz)
Cc: git@vger.kernel.org
Subject: Tip of the day: archaeology
Date: Tue, 13 Dec 2005 13:16:04 -0800	[thread overview]
Message-ID: <7vpso07l63.fsf_-_@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <861x0hxfn2.fsf@blue.stonehenge.com> (Randal L. Schwartz's message of "13 Dec 2005 05:58:41 -0800")

merlyn@stonehenge.com (Randal L. Schwartz) writes:

> I see now that grepping "gitignore" shows git-add.sh and
> git-status.sh.  gitignore is indeed doc'ed in git-add.txt, but not in
> git-status.txt.  Must've snuck in recently.  I'm trying to watch
> "git-whatchanged -p Documentation/*", but I miss things sometimes.

Let me grab this opportunity to demonstrate archaeology tools.

    $ git whatchanged --pretty=oneline \
      -S'--exclude-per-directory=.gitignore' git-status.sh

shows the "Big tool rename" commit 215a7ad on Sep 7th had it as
621fa49 blob, and we can see that the revision:

    $ git cat-file blob 621fa49 | grep -B2 gitignore
            git-ls-files --others \
                --exclude-from="$GIT_DIR/info/exclude" \
                --exclude-per-directory=.gitignore |

already had .gitignore support [*1*].  Looking at the big rename
commit, we learn git-status.sh used to be called as
git-status-script:

    $ git-diff-tree -r -M --name-status 215a7ad | grep status.sh
    R093	git-status-script	git-status.sh

Digging further with the old name reveals that it is this commit:

    $ git whatchanged --pretty=oneline \
      -S'--exclude-per-directory=.gitignore' git-status-script
    diff-tree ba966b9... (from 9804b7d...)
    Teach git-status-script about git-ls-files --others
    :100755 100755 1999a66... 1696f23... M	git-status-script
    $ git cat-file blob 1696f23 | grep gitignore
	    --exclude-per-directory=.gitignore |
    $ git cat-file blob 1999a66 | grep gitignore
    $ git log --max-count=1 ba966b9 | head -n 5
    commit ba966b957908248396402acd785d10ba1da07294
    Author: Junio C Hamano <junkio@cox.net>
    Date:   Fri Aug 26 02:12:50 2005 -0700

        Teach git-status-script about git-ls-files --others


[Footnote]

*1* Sometimes I wish we had "cvs co -p" equivalent.

	$ git cat-blob rev path

Perhaps?

  reply	other threads:[~2005-12-13 21:16 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <7vbqzrcmgr.fsf@assigned-by-dhcp.cox.net>
2005-12-09  5:43 ` as promised, docs: git for the confused linux
2005-12-09  9:43   ` Petr Baudis
2005-12-09 14:01     ` linux
2005-12-09 16:49       ` Randy.Dunlap
2005-12-09 19:12       ` Junio C Hamano
2005-12-09 21:54         ` linux
2005-12-09 23:23           ` Junio C Hamano
2005-12-12 16:34             ` Linus Torvalds
2005-12-12 17:53               ` Timo Hirvonen
2005-12-12 18:18                 ` Linus Torvalds
2005-12-12 20:39                   ` Randal L. Schwartz
2005-12-13  3:58                     ` Joshua N Pritikin
2005-12-13  3:59                       ` Randal L. Schwartz
2005-12-13  5:19                         ` Junio C Hamano
2005-12-13  5:29                           ` Linus Torvalds
2005-12-13  7:18                             ` H. Peter Anvin
2005-12-13  8:01                           ` Junio C Hamano
2005-12-13 13:58                             ` Randal L. Schwartz
2005-12-13 21:16                               ` Junio C Hamano [this message]
2005-12-13 21:54                                 ` Tip of the day: archaeology Linus Torvalds
2005-12-13 22:19                                   ` Junio C Hamano
2005-12-12 17:54               ` as promised, docs: git for the confused Junio C Hamano
2005-12-13  0:22               ` [PATCH] Everyday: some examples Junio C Hamano
2005-12-09 21:33       ` as promised, docs: git for the confused Petr Baudis
2005-12-09  5:44 ` linux
2005-12-10  1:22   ` Junio C Hamano
2005-12-10  8:00   ` Junio C Hamano
2005-12-10 10:56     ` linux

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=7vpso07l63.fsf_-_@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=merlyn@stonehenge.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).