<commit_before># git-gerrit, a gerrit interface

An [ISC-licensed](LICENSE) program which allows for reviewing, downloading,
and querying a Gerrit server via SSH, from the command line.

## Requirements
- [jshon](https://github.com/keenerd/jshon)
- [git](http://git-scm.com)
- ssh
- coreutils (tr, paste, cut, wc, etc.)
- sed
- grep

## Installation
**Exherbo users, there is an exheres in ::somasis; dev-scm/git-gerrit.**

1. `git clone https://github.com/Somasis/git-gerrit` or [download a release].
2. `make`
3. `make install`

## Usage
After installation, run `man git-gerrit`. If you prefer, you can also just do
`git gerrit -h` for a non-manpage help message.

## Rationale
Originally, I had been using OpenStack's `git-review` for using Gerrit in a
more usable interface than plain git. However, it has a few drawbacks:

- Has one main function: pushing patches for review.
- Also can list patches, but the listing is pretty useless and is obviously
  not intended to be one of the main features of the program.
- Code-Review functionality is limited. I don't think there even is any.

In addition, I wanted to teach myself some more about how Gerrit works, and
provide for myself a nice alternative to offerings like `git-review`, and the
more interactive and full-featured `gertty`. `gertty` is also nice, but I<commit_msg>README: add some words about gitreview files<commit_after># git-gerrit, a gerrit interface

An [ISC-licensed](LICENSE) program which allows for reviewing, downloading,
and querying a Gerrit server via SSH, from the command line.

## Requirements
- [jshon](https://github.com/keenerd/jshon)
- [git](http://git-scm.com)
- ssh
- coreutils (tr, paste, cut, wc, etc.)
- sed
- grep

## Installation
**Exherbo users, there is an exheres in ::somasis; dev-scm/git-gerrit.**

1. `git clone https://github.com/Somasis/git-gerrit` or [download a release].
2. `make`
3. `make install`

## Usage
After installation, run `man git-gerrit`. If you prefer, you can also just do
`git gerrit -h` for a non-manpage help message.

Keep in mind, that since `git-gerrit` does aim to an extent to be a
replacement for `git-review`, it actually uses `.gitreview` files for
finding where the repository's Gerrit instance is at. It is currently
compatible with the host and project parameters of `.gitreview` files, and
there's not really much reason to change it.

## Rationale
Originally, I had been using OpenStack's `git-review` for using Gerrit in a
more usable interface than plain git. However, it has a few drawbacks:

- Has one main function: pushing patches for review.
- Also can list patches, but the listing is pretty useless and is obviously
  not intended to be one of the main features of the program.
- Code-Review functionality is limited. I don't think there even is any.

In addition, I wanted to teach myself some more about how Gerrit works, and
provide for myself a nice alternative to offerings like `git-review`, and the
more interactive and full-featured `gertty`. `gertty` is also nice, but I
{'fraction_non_alphanumeric': 0.09193121693121693, 'fraction_numerical': 0.001984126984126984, 'mean_word_length': 4.153321976149915, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 4, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 4, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '843649', 'n_tokens_mistral': 937, 'n_tokens_neox': 889, 'n_words': 432}