[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: BuGit
From: |
Stefan Monnier |
Subject: |
Re: BuGit |
Date: |
Tue, 02 Feb 2016 12:08:22 -0500 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux) |
>> For those curious about what I've been upto lately, one of the things
>> I've been working on is a new distributed issue tracking system which
>> I call BuGit:
>> https://gitlab.com/monnier/bugit
>> It's still primitive (only the command-line UI and the email
>> notification system are more or less complete: the web UI is still
>> read-only, and there is no email UI at all).
> Nice! ...but if I may, why writing it all in bash?
[ Actually it works in dash as well. AFAIK it's almost 99% POSIX shell
code (IIRC the only extension used is to use "type <foo>" to figure out
if <foo> is a valid function/command). ]
The real reason is rather silly: I'd been thinking about how to
represent the database in such a way that all the merging is done "for
free" by the underlying VCS, and when it finally occurred to me, I was
all excited at how simple it was and started to write an email to
a friend outlining how it worked, and since describing it in text was
cumbersome, I started to write it in pseudo-code which quickly turned
into executable sh code.
The next planned feature (email UI) will not be written in sh, and
I expect that after that, all the new code will be in Python.
Stefan
- BuGit, Stefan Monnier, 2016/02/02
- Re: BuGit, Nicolas Petton, 2016/02/02
- Re: BuGit,
Stefan Monnier <=
- Re: BuGit, Aaron Conole, 2016/02/02
- Re: BuGit, Dmitry Gutov, 2016/02/02
- Re: BuGit, Aurélien Aptel, 2016/02/03