From: Junio C Hamano <gitster@pobox.com>
To: "Elijah Newren" <newren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-cvsimport bug with dates
Date: Thu, 15 Nov 2007 22:06:44 -0800 [thread overview]
Message-ID: <7vr6iq207f.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <51419b2c0711152059q55ced86gd224310c8c4a1851@mail.gmail.com> (Elijah Newren's message of "Thu, 15 Nov 2007 21:59:44 -0700")
"Elijah Newren" <newren@gmail.com> writes:
> $ git diff @{2007-10-01}
> warning: Log for '' only goes back to Wed, 24 Oct 2007 19:31:38 +0000.
> fatal: bad object @{2007-10-01}
>
>
> It appears that passing a date to git diff on any repository imported
> by git-cvsimport will show this error, as long as the date is prior to
> when the repository was imported.
That is not a cvsimport specific issue.
When you use "branch@{date}" notation, you are not asking a
question on the project history, but a question on the local
view from _your_ repository on that project.
$ git log --since=3.days.ago master
asks "go back from the master tip and show commits until you hit
the commit made earlier than that date and stop traversing".
On the other hand,
$ git show master@{3.days.ago}
asks "show the commit that was the tip of 'master' branch in my
repository three days ago." Maybe you pulled from your upstream
5 minutes ago, and the last time before that, you pulled three
weeks ago and did not do any development on the branch. In such
a case, the latter question will give you the tip of your
'master' as of three weeks ago which is the same as of three
days ago.
next prev parent reply other threads:[~2007-11-16 6:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 4:59 git-cvsimport bug with dates Elijah Newren
2007-11-16 6:06 ` Junio C Hamano [this message]
2007-11-16 14:12 ` Elijah Newren
2007-11-17 10:12 ` Robin Rosenberg
2007-11-17 15:39 ` Elijah Newren
2007-11-17 21:36 ` Jan Hudec
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=7vr6iq207f.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=newren@gmail.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).