From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Steven Walter" <stevenrwalter@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git-write-tree strangeness
Date: Wed, 8 Aug 2007 18:10:52 +0200 [thread overview]
Message-ID: <81b0412b0708080910u3aee166fo92ea73a4a0a78ccf@mail.gmail.com> (raw)
In-Reply-To: <20070808154211.GA25015@dervierte>
On 8/8/07, Steven Walter <stevenrwalter@gmail.com> wrote:
> I'm importing a large repository from svn into git with a custom tool,
> and I noticed a strange issue with one of the commits.
>
> Upon investigating further, I found that when I ran "git-write-tree"
> followed immediately by "git-diff-index <tree>" I had differences. Does
> that mean that git-write-tree incorrectly recorded the index, or do I
> misunderstand things?
What kind of differences? Different sha1 of content?
I can't simply reproduce it.
next prev parent reply other threads:[~2007-08-08 16:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-08 15:42 git-write-tree strangeness Steven Walter
2007-08-08 16:10 ` Alex Riesen [this message]
2007-08-08 19:39 ` Junio C Hamano
2007-08-08 22:16 ` Steven Walter
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=81b0412b0708080910u3aee166fo92ea73a4a0a78ccf@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=stevenrwalter@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).