From: "Mikael Magnusson" <mikachu@gmail.com>
To: geoffrey.russell@gmail.com
Cc: git@vger.kernel.org
Subject: Re: finding deleted file names
Date: Thu, 3 Jul 2008 05:18:18 +0200 [thread overview]
Message-ID: <237967ef0807022018t31912870gf0490acf5ccef5eb@mail.gmail.com> (raw)
In-Reply-To: <93c3eada0807021945la3e565csc50eed4b14feb9c3@mail.gmail.com>
2008/7/3 Geoff Russell <geoffrey.russell@gmail.com>:
> On Thu, Jul 3, 2008 at 10:42 AM, Mikael Magnusson <mikachu@gmail.com> wrote:
>> 2008/7/3 Geoff Russell <geoffrey.russell@gmail.com>:
>>> git diff --diff-filter=D --name-only HEAD@{'7 days ago'}
>>>
>>> finds files deleted during the last 7 days, but if my repository is
>>> only 6 days old I get a
>>> fatal error.
>>>
>>> fatal: bad object HEAD@{7 days ago}
>>>
>>> Is there something that says "since repository creation", ie., go back as far
>>> as possible, but no further? Is there a symbolic name for the initial commit?
>>
>> There's no symbolic name for it, since there might not be only one initial
>> commit. git.git for example has at least three root commits. You will
>> probably get what you want with $(git rev-list HEAD|tail -1). If your
>> history is very large, $(git rev-list --reverse HEAD|head -1) is slightly
>> faster, but usually not enough to offset typing --reverse :).
>
> Thanks for this, but I'm a little confused.
>
> If I do a "git init", there must be a first commit after this? Isn't
> this the first commit, how
> can there be more than one first commit?
In git.git, the gitk subdirectory has a separate root because it was merged
with the subtree merge strategy, so if you go down the second parent of that
merge commit, you'll end up not at the start of the git history. You can
see this if you just fetch any other repo into your current one and merge it.
Just add everything with conflict markers in if it conflicts and commit,
then look at gitk :). (and obviously then revert the merge or whatever).
Btw, after you git init, there are 0 commits, the first commit is created
when you run git commit the first time.
--
Mikael Magnusson
next prev parent reply other threads:[~2008-07-03 8:25 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 0:01 finding deleted file names Geoff Russell
2008-07-03 1:12 ` Mikael Magnusson
2008-07-03 2:45 ` Geoff Russell
2008-07-03 3:18 ` Mikael Magnusson [this message]
2008-07-03 10:42 ` Jeff King
2008-07-04 6:45 ` Geoff Russell
2008-07-04 7:05 ` Junio C Hamano
2008-07-06 4:54 ` Geoff Russell
2008-07-06 5:17 ` Junio C Hamano
2008-07-07 0:41 ` Geoff Russell
2008-07-03 9:20 ` Jakub Narebski
2008-07-03 10:36 ` Jeff King
2008-07-03 19:41 ` Junio C Hamano
2008-07-03 19:47 ` Jeff King
2008-07-03 20:32 ` Shawn O. Pearce
2008-07-03 11:57 ` Johannes Schindelin
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=237967ef0807022018t31912870gf0490acf5ccef5eb@mail.gmail.com \
--to=mikachu@gmail.com \
--cc=geoffrey.russell@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).