Update upstream llama.cpp by pulling latest upstream and apply all your changes as a patch?
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 40.3k
- Forks
- 3.7k
- PR merge metrics
- No merged PRs in 30d
Description
Hi BitNet team, thanks for the great job!
I know you've done a lot on your fork of llama.cpp and it's difficult to merge back to upstream due to conflicts, but is it possible to pull the latest upstream and apply all your changes as a patch so we can enjoy full functionalities of llama.cpp?
I believe your latest code is in branch merge-dev and involves changes to 34 files.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the merge-dev branch and the 34-file comparison linked in the issue, then compare it with the latest upstream llama.cpp. Determine how the upstream changes and BitNet changes can coexist. Done means the latest upstream functionality is available in BitNet while the existing BitNet changes remain applied.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- machine-learning
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 15/100