git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tomas Carnecky <tomas.carnecky@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: Where did Documentation/perf_counter disappear from linux-2.6-tip.git ?
Date: Tue, 22 Dec 2009 11:04:21 +0100	[thread overview]
Message-ID: <4B3099A5.6040808@gmail.com> (raw)

  $ git --version
git version 1.6.6.rc4

# Documentation/perf_counter is missing from the master branch, so first 
let's find
# out what the last commit was that touched that subdirectory:
$ git log --all -1 -- Documentation/perf_counter
commit 436224a6d8bb3e29fe0cc18122f8d1f593da67b8
Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
Date:   Tue Jun 2 21:02:36 2009 +0200
...
M       Documentation/perf_counter/builtin-report.c

# Great, let's look in which branch that commit is
$ git branch --contains 436224a6d8bb3e29fe0cc18122f8d1f593da67b8
* master

# So, let's look at the log of master and limit it to that subdirectory:
$ git log master -- Documentation/perf_counter
$

# Damn, that doesn't make any sense. In commit 43622 there were files in 
that subdirectory, in master they have gone missing and yet log doesn't 
show any commit touching that subdirectory?
# Let's try something different:
$ git log --diff-filter=D --name-status --all -- Documentation/perf_counter
...

# Ah, now we're getting somewhere, but still no sight of a commit which 
removed for example Documentation/perf_counter/.gitignore
# I'm sure I'm probably just missing a tiny little switch for git-log. I 
also tried other combination of name-status, diff-filter etc, but soon 
after gave up.

tom

             reply	other threads:[~2009-12-22 10:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-22 10:04 Tomas Carnecky [this message]
     [not found] ` <6b08a1ab.3349a908.4b30b80f.ab91f@o2.pl>
2009-12-22 12:23   ` Where did Documentation/perf_counter disappear from linux-2.6-tip.git ? Tomas Carnecky
2009-12-22 18:08 ` Junio C Hamano
2009-12-22 18:18   ` Tomas Carnecky

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=4B3099A5.6040808@gmail.com \
    --to=tomas.carnecky@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).