Convert gitgram/ and aitimemachine/ from embedded git repos (which showed as opaque submodule gitlinks on GitHub) into fully-tracked first-party content. AITM now merges its 7 vendored repos as first-party engines: - memory: beads (Go task DAG) + context7 (docs SDK), unified into saved_contexts - git: vendored C git (bundled binary) + gitnexus (in-process code intelligence) - agentic: a2a (@a2a-js/sdk) + pal (AITM-managed Python subprocess) Includes the full session's product build: Gitgram web/mobile/backend features, AITM website/CLI/MCP, the unified memory layer, engine build tooling (scripts/build-engines.sh, Dockerfile, CI), docs (README, ENGINES.md, ARCHITECTURE.md), and extensive test suites. Build artifacts, node_modules, external/, and gemini-cli are gitignored. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
41 lines
1.3 KiB
Plaintext
41 lines
1.3 KiB
Plaintext
GIT v1.6.2.4 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.6.2.3
|
|
--------------------
|
|
|
|
* The configuration parser had a buffer overflow while parsing an overlong
|
|
value.
|
|
|
|
* pruning reflog entries that are unreachable from the tip of the ref
|
|
during "git reflog prune" (hence "git gc") was very inefficient.
|
|
|
|
* "git-add -p" lacked a way to say "q"uit to refuse staging any hunks for
|
|
the remaining paths. You had to say "d" and then ^C.
|
|
|
|
* "git-checkout <tree-ish> <submodule>" did not update the index entry at
|
|
the named path; it now does.
|
|
|
|
* "git-fast-export" choked when seeing a tag that does not point at commit.
|
|
|
|
* "git init" segfaulted when given an overlong template location via
|
|
the --template= option.
|
|
|
|
* "git-ls-tree" and "git-diff-tree" used a pathspec correctly when
|
|
deciding to descend into a subdirectory but they did not match the
|
|
individual paths correctly. This caused pathspecs "abc/d ab" to match
|
|
"abc/0" ("abc/d" made them decide to descend into the directory "abc/",
|
|
and then "ab" incorrectly matched "abc/0" when it shouldn't).
|
|
|
|
* "git-merge-recursive" was broken when a submodule entry was involved in
|
|
a criss-cross merge situation.
|
|
|
|
Many small documentation updates are included as well.
|
|
|
|
---
|
|
exec >/var/tmp/1
|
|
echo O=$(git describe maint)
|
|
O=v1.6.2.3-38-g318b847
|
|
git shortlog --no-merges $O..maint
|
|
---
|