Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
bulletin
Manage
Activity
Members
Labels
Plan
Issues
Issue boards
Milestones
Wiki
Code
Merge requests
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Build
Pipelines
Jobs
Pipeline schedules
Artifacts
Deploy
Releases
Container registry
Model registry
Operate
Environments
Monitor
Incidents
Analyze
Value stream analytics
Contributor analytics
CI/CD 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
Personal Projects
bulletin
Commits
a5a88706
Commit
a5a88706
authored
9 years ago
by
Kevin Lyda
Browse files
Options
Downloads
Patches
Plain Diff
Some thoughts on how to proceed.
parent
053f8e7a
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
+13
-4
13 additions, 4 deletions
README.md
with
13 additions
and
4 deletions
README.md
+
13
−
4
View file @
a5a88706
...
...
@@ -11,13 +11,13 @@ This repo is not it. It's where I attempt to recreate it.
First, git commits need an author. It would be nice to figure out
the author. The version I used I suspect was written by
[
this guy
](
http://web.mit.edu/london/www/home.html
)
.
[
Mark London
](
http://web.mit.edu/london/www/home.html
)
.
## Where to find BULLETIN
The place to get it seems to be the
[
DECUS archives
](
http://decuslib.com/
)
.
I tracked it down with help from Kent Brodie who I
trac
ed via
I tracked it down with help from Kent Brodie who I
discover
ed via
[
an old USENET post
](
https://groups.google.com/forum/#!search/bulletin$20vms/comp.os.vms/rzM2LQMl6Jo/y1BKhO7dv80J
)
where he too was trying to track the software down. In 1994.
...
...
@@ -48,7 +48,15 @@ tar jcf decus.tar.bz2 decus
This was used to create
`decus.tar.bz2`
which was then extracted as
`decus/`
in this archive.
## Creating the BULLETIN git repo
## Creating the BULLETIN source repo (or branch)
Still trying to decide the end result here. I was going to do a separate
source repo but there's a lot of conversion steps I'd like to capture.
So the
`master`
branch might turn into a
`decus2git`
branch and then once
the gross conversion steps are done, each tape would get it's own orphan
commit branch (with the correct
`GIT_AUTHOR`
and commit info metadata).
Something like
`tapes/DECUS_TAPE_NAME`
. Then the
`master`
branch would
be created by merging in each tape branch in chronological order.
The BULLETIN git repo is created by a shell script,
`mkBULLETIN.sh`
based on edits to the various versions of bulletin that were extracted
...
...
@@ -57,7 +65,8 @@ from the ZIP archives.
The files in the ZIP archives are not ready in their current state to
make the repo. A number of things had to be done to get them ready for
a proper historical source code archive. The commit logs for this repo
cover those steps, but to explain in a bit more detail:
cover those steps, but the following sections explain the steps in
more detail.
### Dependencies
...
...
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