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>
33 lines
1.2 KiB
Plaintext
33 lines
1.2 KiB
Plaintext
Git v1.7.4.3 Release Notes
|
|
==========================
|
|
|
|
Fixes since v1.7.4.2
|
|
--------------------
|
|
|
|
* "git apply" used to confuse lines updated by previous hunks as lines
|
|
that existed before when applying a hunk, contributing misapplication
|
|
of patches with offsets.
|
|
|
|
* "git branch --track" (and "git checkout --track --branch") used to
|
|
allow setting up a random non-branch that does not make sense to follow
|
|
as the "upstream". The command correctly diagnoses it as an error.
|
|
|
|
* "git checkout $other_branch" silently removed untracked symbolic links
|
|
in the working tree that are in the way in order to check out paths
|
|
under it from the named branch.
|
|
|
|
* "git cvsimport" did not bail out immediately when the cvs server cannot
|
|
be reached, spewing unnecessary error messages that complain about the
|
|
server response that it never got.
|
|
|
|
* "git diff --quiet" did not work very well with the "--diff-filter"
|
|
option.
|
|
|
|
* "git grep -n" lacked a long-hand synonym --line-number.
|
|
|
|
* "git stash apply" reported the result of its operation by running
|
|
"git status" from the top-level of the working tree; it should (and
|
|
now does) run it from the user's working directory.
|
|
|
|
And other minor fixes and documentation updates.
|