jj/Cargo.toml

[package]
name = "jujutsu"
version = "0.2.0"
authors = ["Martin von Zweigbergk <martinvonz@google.com>"]
edition = "2021"
license = "Apache-2.0"
description = "Jujutsu (an experimental VCS)"
homepage = "https://github.com/martinvonz/jj"
repository = "https://github.com/martinvonz/jj"
documentation = "https://docs.rs/jujutsu"
readme = "README.md"
keywords = ["VCS", "DVCS", "SCM", "Git", "Mercurial"]
categories = ["command-line-utilities", "development-tools"]

[[bin]]
name = "jj"
path = "src/main.rs"

[[bench]]
name = "diff_bench"
harness = false

[workspace]
members = ["lib"]

[dependencies]
atty = "0.2.14"
chrono = "0.4.19"
clap = { version = "3.1.0", features = ["cargo"] }
clap_complete = "3.1.0"
config = "0.11.0"
criterion = "0.3.5"
git2 = "0.13.25"
hex = "0.4.3"
indoc = "1.0.3"
itertools = "0.10.3"
jujutsu-lib = { version = "=0.2.0", path = "lib"}
maplit = "1.0.2"
pest = "2.1.3"
pest_derive = "2.1.0"
rand = "0.8.4"
tempfile = "3.3.0"
textwrap = "0.14.2"
thiserror = "1.0.30"

[dev-dependencies]
test-case = "1.2.3"
regex = "1.5.4"
criterion = "0.3.5"
criterion_bencher_compat = "0.3.4"
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo 2020-12-12 11:00:42 +03:00			`[package]`
project: rename project from Jujube to Jujutsu "Jujutsu" is probably much more familiar and relatable to most people. Also, I'm still not sure how "jujube" is supposed to be pronounced :P 2021-05-15 19:16:31 +03:00			`name = "jujutsu"`
project: bump version to 0.2.0 for release under new name We need to release on crates.io before the new name gets taken. Besides, a lot has improved since the previous release. 2021-05-15 20:28:40 +03:00			`version = "0.2.0"`
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo 2020-12-12 11:00:42 +03:00			`authors = ["Martin von Zweigbergk <martinvonz@google.com>"]`
cargo: upgrade to Rust 2021 (just to stay up to date) 2021-12-14 08:38:10 +03:00			`edition = "2021"`
cargo: fill in crates.io metadata 2021-01-03 19:45:07 +03:00			`license = "Apache-2.0"`
project: rename project from Jujube to Jujutsu "Jujutsu" is probably much more familiar and relatable to most people. Also, I'm still not sure how "jujube" is supposed to be pronounced :P 2021-05-15 19:16:31 +03:00			`description = "Jujutsu (an experimental VCS)"`
cargo: fill in crates.io metadata 2021-01-03 19:45:07 +03:00			`homepage = "https://github.com/martinvonz/jj"`
			`repository = "https://github.com/martinvonz/jj"`
project: rename project from Jujube to Jujutsu "Jujutsu" is probably much more familiar and relatable to most people. Also, I'm still not sure how "jujube" is supposed to be pronounced :P 2021-05-15 19:16:31 +03:00			`documentation = "https://docs.rs/jujutsu"`
cargo: fill in crates.io metadata 2021-01-03 19:45:07 +03:00			`readme = "README.md"`
			`keywords = ["VCS", "DVCS", "SCM", "Git", "Mercurial"]`
			`categories = ["command-line-utilities", "development-tools"]`
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo 2020-12-12 11:00:42 +03:00
cargo: set binary name to `jj`, not new crate name `jujube` I recently renamed the crate from `jj` to `jujube` because `jj` was taken on crates.io. I didn't realize that that would change the name of the binary. 2021-01-03 21:37:47 +03:00			`[[bin]]`
			`name = "jj"`
			`path = "src/main.rs"`

build: migrate `diff_bench` to `criterion` Benchmarking is currently nightly-only, so to get `jujutsu` to build on stable, we need to use a stable benchmarking library. 2022-02-21 09:21:14 +03:00			`[[bench]]`
			`name = "diff_bench"`
			`harness = false`

cargo: rename crates to names available on crates.io I'm preparing to publish an early version before someone takes the name(s) on crates.io. "jj" has been taken by a seemingly useless project, but "jujube" and "jujube-lib" are still available, so let's use those. 2021-01-03 19:45:07 +03:00			`[workspace]`
			`members = ["lib"]`

import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo 2020-12-12 11:00:42 +03:00			`[dependencies]`
cli: use color only when stdout is a TTY This adds a `ui.color` config that can be set to "always", "never", or "auto". If set to "auto", we use color iff stdout is a TTY. 2021-06-03 08:02:06 +03:00			`atty = "0.2.14"`
cargo: update dependencies For no reason other than to stay up to date. 2020-12-24 07:55:12 +03:00			`chrono = "0.4.19"`
cargo: upgrade clap to 3.1.0 This avoids some deprecation warnings from `cargo install` (which picks the latest version instead of the locked version by default). 2022-02-20 11:25:40 +03:00			`clap = { version = "3.1.0", features = ["cargo"] }`
			`clap_complete = "3.1.0"`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 20:14:21 +03:00			`config = "0.11.0"`
			`criterion = "0.3.5"`
cargo: upgrade dependencies 2022-02-10 09:19:16 +03:00			`git2 = "0.13.25"`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 20:14:21 +03:00			`hex = "0.4.3"`
cargo: update dependencies For no reason other than to stay up to date. 2020-12-24 07:55:12 +03:00			`indoc = "1.0.3"`
cargo: upgrade dependencies 2022-02-10 09:19:16 +03:00			`itertools = "0.10.3"`
project: bump version to 0.2.0 for release under new name We need to release on crates.io before the new name gets taken. Besides, a lot has improved since the previous release. 2021-05-15 20:28:40 +03:00			`jujutsu-lib = { version = "=0.2.0", path = "lib"}`
rewrite: add support for rebasing descendants of multiple rewritten commits I plan to use this for rebasing descendants of rewritten remote branches (on fetch). 2021-09-15 18:54:55 +03:00			`maplit = "1.0.2"`
cargo: update dependencies For no reason other than to stay up to date. 2020-12-24 07:55:12 +03:00			`pest = "2.1.3"`
			`pest_derive = "2.1.0"`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 20:14:21 +03:00			`rand = "0.8.4"`
cargo: upgrade dependencies 2022-02-10 09:19:16 +03:00			`tempfile = "3.3.0"`
cli: add `jj concepts` subcommand for concept help, starting with "branches" With this commit, you can run `jj concepts branches` to get help about the "branches" concept. We don't have much help for other commands and their arguments yet, but I'm starting with concept guides so we can point to them as we add help for commands and their arguments. I initially tried to make the command to get help be `jj help --concept branches`. That would require replacing clap's implementation of the help command with our own. clap-rs/clap#1350 prevented me from doing that. But I'm pretty happy with having it under `jj concepts` anyway. It's probably more discoverable that way. I tried to mimic clap's styling with yellow headings. 2021-09-02 19:06:34 +03:00			`textwrap = "0.14.2"`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 20:14:21 +03:00			`thiserror = "1.0.30"`
import commit 0f15be02bf4012c116636913562691a0aaa7aed2 from my hg repo 2020-12-12 11:00:42 +03:00
			`[dev-dependencies]`
cargo: upgrade dependencies 2022-02-10 09:19:16 +03:00			`test-case = "1.2.3"`
cargo: run `cargo upgrade` For no particular reason other than to stay up to date. 2021-11-30 20:14:21 +03:00			`regex = "1.5.4"`
build: migrate `diff_bench` to `criterion` Benchmarking is currently nightly-only, so to get `jujutsu` to build on stable, we need to use a stable benchmarking library. 2022-02-21 09:21:14 +03:00			`criterion = "0.3.5"`
			`criterion_bencher_compat = "0.3.4"`