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
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Kevin Lyda
vcsh
Commits
4e39f441
Commit
4e39f441
authored
12 years ago
by
Richard Hartmann
Browse files
Options
Downloads
Patches
Plain Diff
README.md: Remove emphasis
parent
980fcd4e
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
+5
-5
5 additions, 5 deletions
README.md
with
5 additions
and
5 deletions
README.md
+
5
−
5
View file @
4e39f441
...
...
@@ -54,21 +54,21 @@ They can all be found [on the author's talk page][talks].
## 3.1 Comparison to Other Solutions ##
Most people who decide to put their dotfiles under version control start with a
**
single repository in $HOME
**
, adding all their dotfiles (and possibly more)
single repository in $HOME, adding all their dotfiles (and possibly more)
to it. This works, of course, but can become a nuisance as soon as you try to
manage more than one host.
The next logical step is to create single-purpose repositories in, for example,
~/.dotfiles and to create
**
symbolic links in $HOME
**
. This gives you the
~/.dotfiles and to create symbolic links in $HOME. This gives you the
flexibility to check out only certain repositories on different hosts. The
downsides of this approach are the necessary manual steps of cloning and
symlinking the individual repositories. It will probably become a nuisance when
you try to manage more than two hosts.
**
vcsh
**
takes this second approach one step further. It expects
**
single-purpose repositories
**
and stores them in a hidden directory (similar
vcsh takes this second approach one step further. It expects
single-purpose repositories and stores them in a hidden directory (similar
to ~/.dotfiles). However, it does not create symbolic links in $HOME; it puts
the
**
actual files right into $HOME
**
.
the actual files right into $HOME.
Furthermore, by making use of [mr] [1], it makes it very easy to enable/disable
and clone a large number of repositories. The use of mr is technically optional
...
...
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