hey! this is a static git repo viewer. commit diffs, file history, older commits and other revisions won't load without javascript.

you are still able to view source files on branch/tag tips, but the experience is degraded.

char-fork/llama.cpp

git clone https://git.t4t.associates/char-fork/llama.cpp

Georgi Gerganovllama.cpp : bump version to 0.3.0 (#27696)c1d0e7a002026-08-25

1Take a look at the changelog between the current version and the previous version - use the `./scripts/make-release-desc.sh [current-version]` to obtain it.
2
3Write a summary of the change log in a few sections:
4
5```
6## Overview
7
8[an overview using 1 to 3 sentences (no line breaks)]
9
10### API changes (if applicable)
11
12[summarize any API changes to `/include/*`, `/tools/mtmd/mtmd.h` and `/tools/server`]
13
14### New models (if applicable)
15
16[summarize new models added to the `src/models/` directory]
17
18### Core changes (if applicable)
19
20[summarize the changes to `/src/*`
21
22### Multi-modality changes (if applicable)
23
24[summarize the changes to `/tools/mtmd/`]
25
26### Server changes (if applicable)
27
28[summarize the changes to `/tools/server/`]
29
30### UI changes (if applicable)
31
32[summarize the changes to `/tools/ui/`]
33
34### ggml changes (if applicable)
35
36[if the version has been updated, link to the respective `ggml` releases on Github, f.ex `https://github.com/ggml-org/ggml/releases/tag/v0.22.0`. for each version bump, lookup the release description and copy the summary here]
37
38```
39
40Guidelines:
41
42- All bullet point in the summary should be concise and rarely exceed a single line of 120 characters
43- Avoid repeating `ggml`-specific changes - these should already be covered by the `ggml` release links
44- Provide PR link for each bullet point where possible
45- Don't add bullet point to state that there are no API changes in some module
46
47Output just the summary in a markdown block, without any extra text.