THthunderbong·May 31, 2026Submission
Qwe: A simple file-first atomic version control system
3 points · Open discussionmainak55512
qwe
Go2025–2026
mainak55512 / qwe
qwe
A simple file-first atomic version control system
2Distinct people
6Mentions
0Explicit recommenders
57GitHub stars
What to know before exploring
What it is
A simple file-first atomic version control system
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
No other repository is repeatedly linked in the same discussions.
This week on Hacker News
Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by month6 dated mentions
Observed mentions: 2025-10-12 18:26:41 UTC to 2026-05-31 07:03:12 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| Oct 2025 | 2025-10-01 00:00:00 UTC | 2025-11-01 00:00:00 UTC | 4 | 4 | 0 |
| Nov 2025 | 2025-11-01 00:00:00 UTC | 2025-12-01 00:00:00 UTC | 0 | 0 | 0 |
| Dec 2025 | 2025-12-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 0 | 0 | 0 |
| Jan 2026 | 2026-01-01 00:00:00 UTC | 2026-02-01 00:00:00 UTC | 0 | 0 | 0 |
| Feb 2026 | 2026-02-01 00:00:00 UTC | 2026-03-01 00:00:00 UTC | 0 | 0 | 0 |
| Mar 2026 | 2026-03-01 00:00:00 UTC | 2026-04-01 00:00:00 UTC | 0 | 0 | 0 |
| Apr 2026 | 2026-04-01 00:00:00 UTC | 2026-05-01 00:00:00 UTC | 0 | 0 | 0 |
| May 2026 | 2026-05-01 00:00:00 UTC | 2026-06-01 00:00:00 UTC | 2 | 2 | 0 |
What Hacker News says
6 sourcesQwe (kiwi): lightweight, flexible, file-first version/revision control system
2 points · Open discussionShow HN: Qwe – Atomic Version Control System
'qwe' is a file-level version/revision control system written purely in Go.
qwe has always focused on file-level version control system, tracking changes to individual files with precision. With this new release, the power of group tracking has been added while maintaining our core design philosophy.
qwe allows you to bundle related files into a single, named snapshot for easy tracking and rollback.
Group Creation: Create a logical group (e.g., "Project X Assets," "Configuration Files") that contains multiple individual files.
Unified Tracking: When you take a snapshot of the group, qwe captures the current state of all files within it. This makes rolling back a set of related changes incredibly simple.
The Flexibility You Need: Individual vs. Group Tracking:
A key design choice in qwe is the persistence of file-level tracking, even withi
Read the rest
n a group. This gives you unparalleled flexibility.
Example: Imagine you are tracking files A, B, and C in a group called "Feature-A." You still have the freedom to commit an independent revision for file A alone without affecting the group's snapshot history for B and C.
This means you can:
- Maintain a clean, unified history for all files in the group (the Group Snapshot).
- Still perform granular, single-file rollbacks or commits outside the group's scope.
This approach ensures that qwe remains the flexible, non-intrusive file revision system that you can rely on.
Show HN: Treat Files as Individual Repository
2 points · Open discussionShow HN: Qwe Version Control System
4 points · Open discussionShow HN: Qwe – Treat standalone files as Individual Repository with qwe rcs
1 points · Open discussion