Re: What's cooking in git.git (Jul 2009, #01; Mon, 06)

From: Christian Couder <chriscool@tuxfamily.org>
Date: Jul 10, 2009, 05:05 UTC
Message-ID: <200907100705.16590.chriscool@tuxfamily.org>
In-Reply-To: <7vk52l4q7k.fsf@alter.siamese.dyndns.org>

On Monday 06 July 2009, Junio C Hamano wrote:

> For the following three series, I have not managed to convince myself if
> these changes have real-world needs.

[...]

Show 16 quoted lines

> * cc/replace (Wed May 27 07:14:09 2009 +0200) 14 commits
>  - t6050: check pushing something based on a replaced commit
>  - Documentation: add documentation for "git replace"
>  - Add git-replace to .gitignore
>  - builtin-replace: use "usage_msg_opt" to give better error messages
>  - parse-options: add new function "usage_msg_opt"
>  - builtin-replace: teach "git replace" to actually replace
>  - Add new "git replace" command
>  - environment: add global variable to disable replacement
>  - mktag: call "check_sha1_signature" with the replacement sha1
>  - replace_object: add a test case
>  - object: call "check_sha1_signature" with the replacement sha1
>  - sha1_file: add a "read_sha1_file_repl" function
>  - replace_object: add mechanism to replace objects found in
>    "refs/replace/"
>  - refs: add a "for_each_replace_ref" function

Didn't you say before that it would be an improvement over grafts?

By the way, may be it would be an improvement to use one bit in "struct object" to mark replaced objects. It could make it easier to spot them where they could make the code behave strangely.

Anyway I will have a 2 week long vacation starting today, so I won't be able to do much soon.

Best regards, Christian.