From: Jonathan Nieder <jrnieder@gmail.com>
To: Samir Faci <samir@esamir.com>
Cc: git@vger.kernel.org
Subject: Re: Git CVS Import Questions
Date: Fri, 30 Jul 2010 15:17:06 -0500 [thread overview]
Message-ID: <20100730201706.GC2448@burratino> (raw)
In-Reply-To: <AANLkTin_d_wKxyJDMbjz4vFacr6GNYzE_aUGi2vbXW3V@mail.gmail.com>
Hi Samir,
Samir Faci wrote:
> mkdir bar; git cvsimport -v Foo/Bar which checks out the history of
> module Bar into the current directory (in this case bar)
>
> now... if I do this again in another directory
>
> mkdir bar2; git cvsimport -v Foo/Bar which repeats the same process
> the hashes don't match up.
Maybe the dates are different? I would suggest comparing the result of
“git fast-export HEAD” from each.
> Now, correct me if I'm wrong.. but I thought the hashes were generated
> based on the content of the diff.
Close, but not quite. This might help: http://progit.org/book/ch9-2.html
Have fun,
Jonathan
prev parent reply other threads:[~2010-07-30 20:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 14:17 Git CVS Import Questions Samir Faci
2010-07-30 20:17 ` Jonathan Nieder [this message]
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=20100730201706.GC2448@burratino \
--to=jrnieder@gmail.com \
--cc=git@vger.kernel.org \
--cc=samir@esamir.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).