Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
V
vcsh
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Container registry
Model registry
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
Repository analytics
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
GitLab community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Kevin Lyda
vcsh
Commits
eaa2b712
Commit
eaa2b712
authored
Jun 9, 2013
by
Richard Hartmann
Browse files
Options
Downloads
Patches
Plain Diff
README.md: Move Introduction to beginning
parent
cde27977
No related branches found
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
README.md
+25
-25
25 additions, 25 deletions
README.md
with
25 additions
and
25 deletions
README.md
+
25
−
25
View file @
eaa2b712
...
...
@@ -3,37 +3,14 @@ vcsh - Version Control System for $HOME (based on git)
# Index #
1.
[
30 second howto
](
#30-second-howto
)
2.
[
Introduction
](
#introduction
)
1.
[
Introduction
](
#introduction
)
2.
[
30 second howto
](
#30-second-howto
)
3.
[
Overview
](
#overview
)
4.
[
Getting Started
](
#getting-started
)
5.
[
Usage
](
#usage
)
6.
[
Contact
](
#contact
)
# 30 second howto #
While it may appear that there's an overwhelming amount of documentation and
while the explanation of the concepts behind
`vcsh`
needs to touch a few gory
details of
`git`
internals, getting started with
`vcsh`
is extremely simple.
Let's say you want to version control your
`vim`
configuration:
vcsh init vim
vcsh vim add ~/.vimrc ~/.vim
vcsh vim commit -m 'Initial commit of my Vim configuration'
# optionally push your files to a remote
vcsh vim remote add origin REMOTE
vcsh vim push origin master:master
If all that looks a _lot_ like standard
`git`
, that's no coincidence; it's
a design feature.
Once you get familiar with
`vcsh`
, it's strongly suggested that you look
into more advanced usage scenarios, especially on how to manage your
`vcsh`
and other repositories with
[
mr
][
mr
]
.
# Introduction #
[
vcsh
][
vcsh
]
allows you to maintain several git repositories in one single
...
...
@@ -60,6 +37,29 @@ a package, yourself. If you do end up packaging `vcsh` please let us know so we
can give you your own packaging branch in the upstream repository.
# 30 second howto #
While it may appear that there's an overwhelming amount of documentation and
while the explanation of the concepts behind
`vcsh`
needs to touch a few gory
details of
`git`
internals, getting started with
`vcsh`
is extremely simple.
Let's say you want to version control your
`vim`
configuration:
vcsh init vim
vcsh vim add ~/.vimrc ~/.vim
vcsh vim commit -m 'Initial commit of my Vim configuration'
# optionally push your files to a remote
vcsh vim remote add origin REMOTE
vcsh vim push origin master:master
If all that looks a _lot_ like standard
`git`
, that's no coincidence; it's
a design feature.
Once you get familiar with
`vcsh`
, it's strongly suggested that you look
into more advanced usage scenarios, especially on how to manage your
`vcsh`
and other repositories with
[
mr
][
mr
]
.
## Talks ##
Some people found it useful to look at slides and videos explaining how
`vcsh`
...
...
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment