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>
40 lines
1.3 KiB
Plaintext
40 lines
1.3 KiB
Plaintext
Git v1.7.2.3 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.7.2.2
|
|
--------------------
|
|
|
|
* When people try insane things such as delta-compressing 4GiB files, we
|
|
threw an assertion failure.
|
|
|
|
* "git archive" gave the full commit ID for "$Format:%h$".
|
|
|
|
* "git fetch --tags" did not fetch tags when remote.<nick>.tagopt was set
|
|
to --no-tags. The command line option now overrides the configuration
|
|
setting.
|
|
|
|
* "git for-each-ref --format='%(objectname:short)'" has been completely
|
|
broken for a long time.
|
|
|
|
* "git gc" incorrectly pruned a rerere record that was created long
|
|
time ago but still is actively and repeatedly used.
|
|
|
|
* "git log --follow -M -p" was seriously broken in 1.7.2, reporting
|
|
assertion failure.
|
|
|
|
* Running "git log" with an incorrect option started pager nevertheless,
|
|
forcing the user to dismiss it.
|
|
|
|
* "git rebase" did not work well when the user has diff.renames
|
|
configuration variable set.
|
|
|
|
* An earlier (and rather old) fix to "git rebase" against a rebased
|
|
upstream broke a more normal, non rebased upstream case rather badly,
|
|
attempting to re-apply patches that are already accepted upstream.
|
|
|
|
* "git submodule sync" forgot to update the superproject's config file
|
|
when submodule URL changed.
|
|
|
|
* "git pack-refs --all --prune" did not remove a directory that has
|
|
become empty.
|