Re: RFC: grafts generalised
From: Dmitry Potapov <hidden>
Date: 2016-06-15 22:44:52
On Wed, Jul 02, 2008 at 04:35:19PM +0200, Stephen R. van den Berg wrote:
_ - Extend the grafts file format to support something like the following syntax: _ commit eb03813cdb999f25628784bb4f07b3f4c8bfe3f6 Parent: 7bc72e647d54c2f713160b22e2e08c39d86c7c28 Merge: 3b3da24960a82a479b9ad64affab50226df02abe 13b8f53e8ccec3b08eeb6515e6a10a2a Merge: ac719ed37270558f21d89676fce97eab4469b0f1 Tree: 32fc99814b97322174dbe97ec320cf32314959e2 Author: Foo Bar (FooBar) <foo@bar> AuthorDate: Sat Jun 6 13:50:44 1998 +0000 Commit: Foo Bar (FooBar) <foo@bar> CommitDate: Sat Jun 7 13:50:44 1998 +0000 Logmessage: First line of logmessage override Logmessage: Second line of logmessage override Logmessage: Etc.
I don't think that the grafts file is the right place for this kind of information. Perhaps, it would be better to have a separate file or even a directory with files where commit-id identifies a text file with a new commit object, which should be placed instead of an old one. So, it will be easy to tell git filter-branch to use this new information. However, if you want more than just ability to edit commits in a text file but also inspect changes using normal git commands and gitk (as it is possible with grafts), it will require changes to the git core, which, perhaps, not difficult to implement using pretend_sha1_file(), but I am not sure that everyone will welcome that... Dmitry