Update README to include Scalar CLI details #377
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This set of edits does only minor edits to the README content, including: 1. Word wrapping to 100 characters. 2. Updating the installation instructions to use v2.32.0.vfs.0.2 3. Replace uses of "Microsoft Git" with `microsoft/git` Signed-off-by: Derrick Stolee <[email protected]>
These docs have been altered to fit the version implemented in C within microsoft/git. This means in particular that the advanced.md file no longer applied at all. Some other areas were removed or significantly edited. Signed-off-by: Derrick Stolee <[email protected]>
Add a section about how the Scalar CLI is included in microsoft/git. Signed-off-by: Derrick Stolee <[email protected]>
Edit the explaination of why this fork exists and its relationship to the GVFS protocol. Signed-off-by: Derrick Stolee <[email protected]>
Add instructions to check `scalar version`. Signed-off-by: Derrick Stolee <[email protected]>
Add "and the Scalar CLI" to the header of the README Signed-off-by: Derrick Stolee <[email protected]>
derrickstolee
requested review from
dscho,
mjcheetham,
jeffhostetler,
ldennington and
prplr
jeffhostetler
approved these changes
Jun 16, 2021
derrickstolee
commented
Jun 16, 2021
Signed-off-by: Derrick Stolee <[email protected]>
Signed-off-by: Derrick Stolee <[email protected]>
dscho
reviewed
Jun 16, 2021
dscho
reviewed
Jun 16, 2021
dscho
reviewed
Jun 16, 2021
dscho
reviewed
Jun 16, 2021
dscho
reviewed
Jun 16, 2021
dscho
approved these changes
Jun 16, 2021
Typo noticed by Johannes. Signed-off-by: Derrick Stolee <[email protected]>
Typos and a reference to git-maintenance builtin. Signed-off-by: Derrick Stolee <[email protected]>
|
Darn, there's the "unable to access global gitconfig: Permission denied" problem again. I guess I will have to prioritize fixing it. But the PR looks good, I think it is ready. |
ldennington
reviewed
Jun 17, 2021
Fix build-from-source instructions. Signed-off-by: Derrick Stolee <[email protected]>
@ldennington I just use VS Code and have this in my The |
Awesome, thanks! |
derrickstolee
added a commit
that referenced
this pull request
Aug 3, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Aug 3, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Aug 5, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
dscho
pushed a commit
that referenced
this pull request
Aug 5, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Aug 9, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Aug 12, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Aug 17, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
dscho
pushed a commit
that referenced
this pull request
Oct 30, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Oct 30, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Oct 31, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Nov 4, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Nov 10, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
derrickstolee
added a commit
that referenced
this pull request
Nov 15, 2021
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 12, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 19, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 20, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 20, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 20, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 20, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 20, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 20, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 25, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
ldennington
pushed a commit
to ldennington/git
that referenced
this pull request
Jan 25, 2022
… details I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
dscho
pushed a commit
that referenced
this pull request
Feb 1, 2022
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
dscho
pushed a commit
that referenced
this pull request
Jun 17, 2022
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
dscho
pushed a commit
that referenced
this pull request
Jun 17, 2022
I created these as `fixup!` commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit. * The first is a doozy, adjusting line widths and otherwise updating some minor things here and there. * The rest are small and explained by the body of the commit messages. * One non-`fixup!` commit adds the `docs/` directory from `microsoft/scalar`, with some edits due to the C port of Scalar.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I created these as
fixup!commits so they get squashed in the next major release rebase, but also so they can be reviewed commit-by-commit.fixup!commit adds thedocs/directory frommicrosoft/scalar, with some edits due to the C port of Scalar.