git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Nguyen Thai Ngoc Duy <pclouds@gmail.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH RFC] parse_object: pass on the original sha1, not the  replaced one
Date: Wed, 4 Aug 2010 22:42:50 +1000	[thread overview]
Message-ID: <AANLkTimPQcZN-ASP+N+h9GaOSkgbnyNxiSktL+z-nBRu@mail.gmail.com> (raw)
In-Reply-To: <201008041358.13081.chriscool@tuxfamily.org>

On Wed, Aug 4, 2010 at 9:58 PM, Christian Couder
<chriscool@tuxfamily.org> wrote:
>> > I will
>> > try to have a deeper look at that, but it would help if you could give
>> > an example of a command that triggers this behavior.
>>
>> The following patch add "sha1" command. These commands give different sha1:
>>
>> git sha1 `git rev-parse HEAD` `git rev-parse HEAD^` A
>> git sha1 `git rev-parse HEAD` `git rev-parse HEAD^` B
>
> Yes, but that does not mean that the content of the object returned by
> lookup_commit(A) is not the content of A.
>
> Or do you have an example where the content of the object returned by
> lookup_commit(A) is not the content of A?

Both return the content of B. I modified my patch a bit to also show
the content, ((struct commit*)obj)->buffer.

$ ./git cat-file -p HEAD
tree 13109340ff2bd55bd16271bbad7a9232f9052923
parent 9a3028b987d73e4c85e8db9980720feba6a1b5c6
parent 2aedccd3d51ec922020f7c7e39df5d2c4d3af515
author Junio C Hamano <gitster@pobox.com> 1280274846 -0700
committer Junio C Hamano <gitster@pobox.com> 1280274905 -0700

Sync with 1.7.2.1

Signed-off-by: Junio C Hamano <gitster@pobox.com>

$ ./git cat-file -p HEAD^
tree 4ffcd88bed7a675e2d130a41203a7ebe026b6462
parent 9a9fb5d3c4c8601beb2d7b8e3b9283c6c3815a2d
author Ævar Arnfjörð Bjarmason <avarab@gmail.com> 1279925924 +0000
committer Junio C Hamano <gitster@pobox.com> 1280124888 -0700

tests: Ignore the Test::Harness .prove file

We document how to run prove with the --state option in t/README. This
produces a .prove YAML file in the current directory. Change the t/
gitignore to ignore it, and clean it up on `make clean'.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

$ ./git sha1 `git rev-parse HEAD` `git rev-parse HEAD^` A
old  = ba9523ea809dc496a14f3644bdc1dd6f486983c0
new  = 9a3028b987d73e4c85e8db9980720feba6a1b5c6
sha1 = 9a3028b987d73e4c85e8db9980720feba6a1b5c6
tree 4ffcd88bed7a675e2d130a41203a7ebe026b6462
parent 9a9fb5d3c4c8601beb2d7b8e3b9283c6c3815a2d
author Ævar Arnfjörð Bjarmason <avarab@gmail.com> 1279925924 +0000
committer Junio C Hamano <gitster@pobox.com> 1280124888 -0700

tests: Ignore the Test::Harness .prove file

We document how to run prove with the --state option in t/README. This
produces a .prove YAML file in the current directory. Change the t/
gitignore to ignore it, and clean it up on `make clean'.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>

$ ./git sha1 `git rev-parse HEAD` `git rev-parse HEAD^` B
old  = ba9523ea809dc496a14f3644bdc1dd6f486983c0
new  = 9a3028b987d73e4c85e8db9980720feba6a1b5c6
sha1 = ba9523ea809dc496a14f3644bdc1dd6f486983c0
tree 4ffcd88bed7a675e2d130a41203a7ebe026b6462
parent 9a9fb5d3c4c8601beb2d7b8e3b9283c6c3815a2d
author Ævar Arnfjörð Bjarmason <avarab@gmail.com> 1279925924 +0000
committer Junio C Hamano <gitster@pobox.com> 1280124888 -0700

tests: Ignore the Test::Harness .prove file

We document how to run prove with the --state option in t/README. This
produces a .prove YAML file in the current directory. Change the t/
gitignore to ignore it, and clean it up on `make clean'.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
-- 
Duy

  reply	other threads:[~2010-08-04 12:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-31 12:36 [PATCH RFC] parse_object: pass on the original sha1, not the replaced one Nguyễn Thái Ngọc Duy
2010-08-02  7:42 ` Christian Couder
2010-08-02  9:31   ` Nguyen Thai Ngoc Duy
2010-08-03  5:00     ` Christian Couder
2010-08-03  6:01       ` Nguyen Thai Ngoc Duy
2010-08-04 11:58         ` Christian Couder
2010-08-04 12:42           ` Nguyen Thai Ngoc Duy [this message]
2010-08-04 12:57             ` Christian Couder
2010-08-04 22:07               ` Nguyen Thai Ngoc Duy
2010-08-05 11:41                 ` Christian Couder
2010-08-07  4:03                   ` Nguyen Thai Ngoc Duy
2010-08-13  3:59                     ` Christian Couder
2010-08-13  9:02                       ` Nguyen Thai Ngoc Duy
2010-08-14  2:03                         ` Christian Couder

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=AANLkTimPQcZN-ASP+N+h9GaOSkgbnyNxiSktL+z-nBRu@mail.gmail.com \
    --to=pclouds@gmail.com \
    --cc=chriscool@tuxfamily.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).