JakeHillion/nixpkgs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
211,221 Commits 2 Branches 0 Tags 13 GiB
e4f65629db
Commit Graph

21 Commits

Author SHA1 Message Date
Maximilian Bosch
7f723b128b
cargo-make: 0.26.1 -> 0.26.2 
https://github.com/sagiegurari/cargo-make/releases/tag/0.26.2
 2020-01-24 13:38:22 +01:00
Maximilian Bosch
4c58a2d2c7
cargo-make: 0.26.0 -> 0.26.1 
https://github.com/sagiegurari/cargo-make/releases/tag/0.26.1
 2020-01-17 20:15:33 +01:00
Maximilian Bosch
384d963920
cargo-make: 0.25.1 -> 0.26.0 
https://github.com/sagiegurari/cargo-make/releases/tag/0.26.0
 2020-01-10 12:56:48 +01:00
Maximilian Bosch
f0e3140e68
cargo-make: 0.25.0 -> 0.25.1 
https://github.com/sagiegurari/cargo-make/releases/tag/0.25.1
 2020-01-03 16:33:00 +01:00
Maximilian Bosch
26f3d45b5f
cargo-make: 0.24.3 -> 0.25.0 
https://github.com/sagiegurari/cargo-make/releases/tag/0.25.0
 2020-01-01 21:13:45 +01:00
Maximilian Bosch
43eec1d30f
cargo-make: 0.24.2 -> 0.24.3 
https://github.com/sagiegurari/cargo-make/releases/tag/0.24.3
 2019-12-31 20:30:12 +01:00
Maximilian Bosch
9842c4b107
treewide: update which packages I'm currently maintaining 
Idea shamelessly stolen from 4e60b0efae.

I realized that I don't really know anymore where I'm listed as maintainer and what
I'm actually (co)-maintaining which means that I can't proactively take
care of packages I officially maintain.

As I don't have the time, energy and motivation to take care of stuff I
was interested in 1 or 2 years ago (or packaged for someone else in the
past), I decided that I make this explicit by removing myself from several
packages and adding myself in some other stuff I'm now interested in.

I've seen it several times now that people remove themselves from a
package without removing the package if it's unmaintained after that
which is why I figured that it's fine in my case as the affected pkgs
are rather low-prio and were pretty easy to maintain.
 2019-12-26 15:27:47 +01:00
Maximilian Bosch
69d31c37bc
cargo-make: 0.24.1 -> 0.24.2 
https://github.com/sagiegurari/cargo-make/releases/tag/0.24.2
 2019-12-14 02:25:41 +01:00
Maximilian Bosch
b3c9e72ef5
cargo-make: 0.24.0 -> 0.24.1 
https://github.com/sagiegurari/cargo-make/releases/tag/0.24.1
 2019-12-06 17:22:51 +01:00
Maximilian Bosch
8960509fc5
cargo-make: 0.23.0 -> 0.24.0 
https://github.com/sagiegurari/cargo-make/releases/tag/0.24.0
 2019-11-22 19:16:13 +01:00
Maximilian Bosch
1737cd07ca
cargo-make: 0.22.2 -> 0.23.0 
https://github.com/sagiegurari/cargo-make/releases/tag/0.23.0

Please note that the cargo hash didn't change since no dependencies were
updated (only the package version in Cargo.lock).
 2019-10-16 12:43:58 +02:00
Maximilian Bosch
e071809101
cargo-make: 0.22.1 -> 0.22.2 
https://github.com/sagiegurari/cargo-make/releases/tag/0.22.2

Also regenerated the lockfile and added it to the repo itself rather
than fetching it from a GitHub gist.
 2019-10-15 12:06:39 +02:00
xrelkd
e93f1175db cargo-make: 0.22.0 -> 0.22.1 2019-08-21 09:59:10 +08:00
xrelkd
db3f4a3149 cargo-make: 0.21.0 -> 0.22.0 2019-08-15 11:26:39 +08:00
xrelkd
43c779ca92 cargo-make: 0.20.0 -> 0.21.0 2019-06-27 12:37:48 +08:00
xrelkd
71ce2a1cd3 cargo-make: 0.19.5 -> 0.20.0 2019-06-16 22:51:51 +08:00
xrelkd
cf65af601c cargo-make: 0.19.4 -> 0.19.5 2019-06-10 10:27:05 +08:00
xrelkd
e9d3a570a6 cargo-make: 0.19.3 -> 0.19.4 2019-06-01 22:54:05 +08:00
xrelkd
cb9b203068 cargo-make: 0.19.2 -> 0.19.3 2019-05-28 10:51:28 +08:00
xrelkd
aa90dc21b5 cargo-make: 0.19.1 -> 0.19.2 2019-05-27 09:41:50 +08:00
xrelkd
c1756a0628
cargo-make: init at 0.19.1 2019-05-15 22:25:30 -05:00