packages feed

lentil 1.0.0.0 → 1.0.0.1

raw patch · 5 files changed

+31/−24 lines, 5 files

Files

changes.txt view
@@ -1,3 +1,9 @@+1.0.0.1+-------++- Released Fri 02 Sep 2016 17:39:11 CEST+- Fixed stack.yaml+ 1.0.0.0 ------- 
issues.txt view
@@ -7,35 +7,32 @@     13  html report, come hlint [feature:advanced]     14  symlinks? [feature:intermediate]     15  check --output pretty, there are trailing white spaces [bug] [u:1]-    16  test con 7.6.3 [feature:basic] [test]-    17  autoignore non-text files? (binary, images, bloom filter) [2016]-    18  da cabal a hpack [u:1] [feature:advanced]-    19  sm: issue numbers is valuable [design] [request]-    20  sm: have a way to link to discussion/history of issue [design]+    16  autoignore non-text files? (binary, images, bloom filter) [2016]+    17  sm: issue numbers is valuable [design] [request]+    18  sm: have a way to link to discussion/history of issue [design]         [request]-    21  sm: 1. lentil autogenerates numbers where missing adding tags, 2.+    19  sm: 1. lentil autogenerates numbers where missing adding tags, 2.         creates an associated numbered file in .issues/, displays         associated notes written in those files is asked, 3. even update         them when there is a source change. (4) these files could be         webserved when they want something linkable. Vedi comments in         doc/dev/issues.txt [design] [request]-    27  chickpea, lentil's brother. Two commands, add number to numberless+    25  chickpea, lentil's brother. Two commands, add number to numberless         tag (#1212 or something), create a mini db with those issues, which         automatically updated and you can even write stuff in there. O         maybe you can even add lentil, chickpea and quinoa. Vedi more in         doc/dev/issues.txt [design]-    33  make it lazy in ouputting todos [refactor]-    34  way to 'group' (section) output by tag [feature:advanced]-    35  win (and mac?) builds [package] [u:3] [2016]-    36  Henning: don't output nothing on lentil xxx.cabal (maybe add 19+    31  way to 'group' (section) output by tag [feature:advanced]+    32  win (and mac?) builds [package] [u:3] [2016]+    33  Henning: don't output nothing on lentil xxx.cabal (maybe add 19         skipped?) [request] [2016]-    37  code coverage [test]-    38  add .lentilignore (or even .lentilconf) Michał Antkiewicz+    34  code coverage [test]+    35  add .lentilignore (or even .lentilconf) Michał Antkiewicz         [feature:intermediate] [request]-    40 +    37     https://blog.steve.org.uk/If_line_noise_is_a_program__all_fuzzers_are_developers.html    in lentil? [debug] [u:2]-    41  parsing with http://awgn.github.io/cgrep/ [design]+    38  parsing with http://awgn.github.io/cgrep/ [design]   src/Lentil/Args.hs     26  disambiguation optparse-applicative [feature:intermediate]@@ -46,12 +43,12 @@     36  maybe use a dedicated library to format xml? [design]   src/Lentil/File.hs-    41  not using canonised paths because it is extremely slow on big+    40  not using canonised paths because it is extremely slow on big         repositories (like darcs). Explore different possibilities         (conduit, new Filepath, unix program). [u:2] [duct]-    52  apparently toListM is not idiomatic [refactor] [duct]-    66  use pipes-files when released [feature:intermediate]-    77  combine funziona su windows? [feature:intermediate]+    51  apparently toListM is not idiomatic [refactor] [duct]+    65  use pipes-files when released [feature:intermediate]+    76  combine funziona su windows? [feature:intermediate]   src/Lentil/Parse/Issue.hs     30  "feature" flagword could (in theory) clash with a free-text comment@@ -61,9 +58,10 @@   src/Lentil/Parse/Run.hs     58  a function String -> [Issue]-    80  personally i don't like when the leading character of the progress-        bar is different [feeback] [request]-    97  sicuramente c'è un modo più elegante e breve [refactor] [duct]+    80  <qptain> personally i don't like when the leading character of the+        progress bar is different [feeback] [request]+    97  sicuramente c'è un modo più elegante e breve. Ah! quando mettono le+        tuples section! [refactor] [duct]   src/Lentil/Parse/Syntaxes.hs     33  add langparsers che sia estensibile e leggibile a compilazione
lentil.cabal view
@@ -1,5 +1,5 @@ name:                lentil-version:             1.0.0.0+version:             1.0.0.1 synopsis:            frugal issue tracker description:         minumum effort, cohesive issue tracker based on                      ubiquitous @TODO@s and @FIXME@s conventions.
src/Main.hs view
@@ -28,7 +28,7 @@                                    short 'v'      <>                                    help "show version and copyright info" )     where-          versionCopy = "\nlentil - frugal issue tracker, version 1.0.0.0\n\+          versionCopy = "\nlentil - frugal issue tracker, version 1.0.0.1\n\                         \(C) 2015-2016 Francesco Ariis - http://www.ariis.it\n\                         \released under the GNU General Public License v3\n" 
stack.yaml view
@@ -1,3 +1,6 @@ resolver: lts-6.14 packages: - '.'+extra-deps:+  - optparse-applicative-0.13.0.0+  - pipes-4.2.0