| commit | 9585cb8d964a1f17895d58b280b5adf62265be53 | |
| author | Jonathan Nieder <jrnieder@gmail.com> | |
| Tue, 31 Mar 2015 23:18:07 +0000 (31 16:18 -0700) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Wed, 1 Apr 2015 00:02:29 +0000 (31 17:02 -0700) | ||
| tree | 71c96c5bf953d36442a65910ba73fbe1159e8a90 | treesnapshot (tar.gz zip) |
| parent | e156455ea49124c140a67623f22a393db62d5d98 | commitdiff |
fast-import doc: remove suggested 16-parent limit
Merges with an absurd number of parents are still a bad idea because
they do not render well in tools like gitk, but if they are present
in the repository being imported into git then there's no need to
avoid reproducing them faithfully.
In olden times, before v1.6.0-rc0~194 (2008-06-27), git commit-tree
and higher-level tools built on top of it were limited to writing 16
parents for a commit. Nowadays normal git operations are happy to
write more parents when asked, so the motivation for this note in the
fast-import documentation is gone and we can remove it.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Merges with an absurd number of parents are still a bad idea because
they do not render well in tools like gitk, but if they are present
in the repository being imported into git then there's no need to
avoid reproducing them faithfully.
In olden times, before v1.6.0-rc0~194 (2008-06-27), git commit-tree
and higher-level tools built on top of it were limited to writing 16
parents for a commit. Nowadays normal git operations are happy to
write more parents when asked, so the motivation for this note in the
fast-import documentation is gone and we can remove it.
Signed-off-by: Jonathan Nieder <jrnieder@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| Documentation/git-fast-import.txt | diffblobblamehistory |