Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
F
forge001
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Snippets
Deploy
Releases
Package registry
Model registry
Operate
Terraform modules
Monitor
Incidents
Service Desk
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
Terms and privacy
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
Gerhard Gonter
forge001
Commits
d1030242
Commit
d1030242
authored
Jul 21, 2014
by
Gerhard Gonter
Browse files
Options
Downloads
Patches
Plain Diff
fixed typos in POD section
parent
fc6211a7
Branches
Branches containing commit
No related tags found
No related merge requests found
Changes
1
Show whitespace changes
Inline
Side-by-side
Showing
1 changed file
textarchive/vlib001.pl
+4
-4
4 additions, 4 deletions
textarchive/vlib001.pl
with
4 additions
and
4 deletions
textarchive/vlib001.pl
+
4
−
4
View file @
d1030242
...
...
@@ -524,7 +524,7 @@ __END__
* specifing the store should be optional.
* environment variable TABASE:
* add pod section
* allow command line option to specif
i
y alternative base directory name
* allow command line option to specify alternative base directory name
=head2 misc
...
...
@@ -533,17 +533,17 @@ __END__
* also, checking the VCS status (if not committing updates)
might be useful.
* other hashing algorithms:
* currently we use md5 for hashing, however, this co
ul
d should
* currently we use md5 for hashing, however, this cod
e
should
be fairly simple to adopt for sha1, sha256 or something else.
* possibly, it makes sense to allow several hashing algorithms
in parallel, however, then it might be a good idea to store
file metadata in one place and let other hashes point to that
place.
* make
i
t available for the "reposync" project
* make t
his code
available for the "reposync" project
=head2 embedded databases?
* maybe embedded MongoDB would be a nice alternative to the full
blown
service base
MongoDB backend
blown
TCP/IP connected
MongoDB backend
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