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. Please, don't. It adds completely unnecessary complexity and it is _not_ grafting anymore - look the word up in a dictionary. :-) Have a look at what you wrote above - now, Git already has a way to store all this information, right? In the commit objects! So, the real solution is to take the commit objects you want to modify, create new commit objects, then graft the new commit on all the old commit children. It fits neatly in the Git philosophy, there is no need at all to tweak the current infrastructure for this and it should be trivial to automate, too. -- Petr "Pasky" Baudis The last good thing written in C++ was the Pachelbel Canon. -- J. Olson -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
