So:
* Binary is a no no.
* Issues are stored in one way or another as mail(s).
* That sits under a version control.
And an issue has the fields:
* status
* id
* project
I am guessing what project it belongs to will already be in the address fileld.
and the id will be in the subject.
If foldere
Most issue tracker entries are full of stupid garbage we don't want
anyway. What worked great was the script we once had on the wmii irc
channel which just appended sentences beginning with BUG to the
buggfile.
Editing the sentences and then deleting all useless entries or
redundant letters keeps e
I like the idea of maildir-in-git, it makes something like automatically
generating a website trivial with hooks.
On Fri, Jan 13, 2012 at 11:35:33PM +0100, Paul Onyschuk wrote:
> On Fri, 13 Jan 2012 22:48:04 +0100
> markus schnalke wrote:
>
> >
> > Unless you want to make changes ...
> >
>
> "
On Fri, 13 Jan 2012 22:48:04 +0100
markus schnalke wrote:
>
> Unless you want to make changes ...
>
"Abandon all hope, ye who enter here". My personal workaround is to
join IRC channel (or spam mailing list) and force developer/commiter to
create issue. Ugly hack, but works most of the times.
On Fri, Jan 13, 2012 at 21:48:47 +, Bjartur Thorlacius wrote:
> >This problem would come up if there was only one tagset and each monitor
> >would be an independent view whose visible tags could be set independently.
> >I rather meant that there should be only one tagset, and all monitors
> >to
On Fri, Jan 13, 2012 at 11:35:02AM +0100, Thomas Dean wrote:
> On Thu, Jan 12, 2012 at 17:44:56 -0500, TJ Robotham wrote:
> > You might find it helpful to go into sendmon and delete that one line that
> > resets the window's tags to whatever's currently visible on the other
> > monitor.
> > That w
Þann fös 13.jan 2012 10:32, skrifaði Thomas Dean:
This problem would come up if there was only one tagset and each monitor
would be an independent view whose visible tags could be set independently.
I rather meant that there should be only one tagset, and all monitors
together would form a combin
[2012-01-13 17:28] Paul Onyschuk
> On Fri, 13 Jan 2012 15:48:43 +0100
> markus schnalke wrote:
>
> Mbox formats are human readable, and file per issues makes it
> accessible. Throwing everything into one file (like mbox mail archive)
> or splitting everything into zillon files (file per message l
On Fri, Jan 13, 2012 at 11:32:42AM +0100, Thomas Dean wrote:
> This problem would come up if there was only one tagset and each monitor
> would be an independent view whose visible tags could be set independently.
> I rather meant that there should be only one tagset, and all monitors
> together wo
On Fri, 13 Jan 2012 13:17:13 -0500
Kurt H Maier wrote:
>
> debbugs is a bit overblown. As a systems administrator I've had the
> profound displeasure of interacting with dozens of issue trackers over
> the years; everything from RT to Trac to JIRA and on and on. The
> problem is always the same
On Fri, Jan 13, 2012 at 05:28:19PM +0100, Paul Onyschuk wrote:
> What makes old plain TODO interesting is zero setup offline usage and
> direct access to data (checkout repository and open in your favorite
> editor).
and then it turns into a huge mess when some vim nerd has expandtab
turned on.
>
On Fri, 13 Jan 2012 15:48:43 +0100
markus schnalke wrote:
>
> No, put meta information in the header, where it belongs to. anno(1)
> from MH does it for you.
>
> Any newer message might change these attributes. Well, you might want
> to update these attributes in the first message, to have the l
[2012-01-13 15:27] Paul Onyschuk
>
> - treat first message in mbox as meta: modify and store common
> informations (priority, short description, category of issue and so on)
> there
No, put meta information in the header, where it belongs to. anno(1)
from MH does it for you.
Any newer message m
On Thu, 12 Jan 2012 19:34:09 +0200
aecepoglu@ wrote:
>
> I might be interested in trying to help write one such suckless issue
> tracker as requested on the webpage.
>
> I just want to ask;
> What set of features are a must for you?
>
After reading some discussion I have some ideas. For small
On Thu, Jan 12, 2012 at 17:44:56 -0500, TJ Robotham wrote:
> > But with two monitors, I constantly find myself moving windows between the
> > two, and searching for windows that I "lost" because I put them on the other
> > monitor, which makes them lose their previously assigned tags.
>
> You migh
On Thu, Jan 12, 2012 at 18:09:15 +, Rob wrote:
> > I would imagine that the (or my at least) workflow could be much smoother
> > if there was only one tagset, independently of the number of monitors, and
> > if there were (a) layout(s) suitable for multi-screen views. The first
> > useful layou
2012/1/12 markus schnalke
> [2012-01-12 19:06] Anselm R Garbe
> > On 12 January 2012 18:34, wrote:
> > >
> > > I might be interested in trying to help write one such suckless
> > > issue tracker as requested on the webpage.
> > >
> > > I just want to ask;
> > > What set of features are a must
17 matches
Mail list logo
