From df0892351a394d768489b5647d47b73c24d3ef5f Mon Sep 17 00:00:00 2001 From: Sebastian Thiel Date: Wed, 2 Jun 2010 00:48:16 +0200 Subject: commit: initial version of commit_from_tree which could create commit objects if it could serialize itself --- CHANGES | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) (limited to 'CHANGES') diff --git a/CHANGES b/CHANGES index 5d677b06..e24e723d 100644 --- a/CHANGES +++ b/CHANGES @@ -1,7 +1,11 @@ ======= CHANGES ======= - + +0.2 Beta 2 +=========== + * Commit objects now carry the 'encoding' information of their message. It wasn't parsed previously, and defaults to UTF-8 + 0.2 ===== General -- cgit v1.2.3 From 1e2b46138ba58033738a24dadccc265748fce2ca Mon Sep 17 00:00:00 2001 From: Sebastian Thiel Date: Thu, 3 Jun 2010 23:20:34 +0200 Subject: commit.create_from_tree now uses pure python implementation, fixed message parsing which truncated newlines although it was ilegitimate. Its up to the reader to truncate therse, nowhere in the git code I could find anyone adding newlines to commits where it is written Added performance tests for serialization, it does about 5k commits per second if writing to tmpfs --- CHANGES | 1 + 1 file changed, 1 insertion(+) (limited to 'CHANGES') diff --git a/CHANGES b/CHANGES index e24e723d..e9e1257e 100644 --- a/CHANGES +++ b/CHANGES @@ -5,6 +5,7 @@ CHANGES 0.2 Beta 2 =========== * Commit objects now carry the 'encoding' information of their message. It wasn't parsed previously, and defaults to UTF-8 + * Commit.create_from_tree now uses a pure-python implementation, mimicing git-commit-tree 0.2 ===== -- cgit v1.2.3