Skip to content

Commit

Permalink
Makefile: bump version to 1.0
Browse files Browse the repository at this point in the history
  • Loading branch information
billziss-gh committed Mar 8, 2022
1 parent 4b90500 commit c2c5221
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
4 changes: 2 additions & 2 deletions Makefile
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
# Makefile

MyBuildNumber = $(shell date +%y%j)
MyVersion = 0.2.$(MyBuildNumber)
MyProductVersion = "2022 Beta2"
MyVersion = 1.0.$(MyBuildNumber)
MyProductVersion = "2022 Beta1"
MyProductStage = "Beta"

MyProductName = "HUBFS"
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ By default HUBFS presents the following file system hierarchy: / *owner* / *repo

HUBFS interprets submodules as symlinks. These submodules can be followed if they point to other GitHub repositories. General repository symlinks should work as well. (On Windows you must use the FUSE option `rellinks` for this to work correctly.)

With release 2022 Beta2 HUBFS *ref* directories are now writable. This is implemented as a union file system that overlays a read-write local file system over the read-only Git content. This scheme allows files to be edited and builds to be performed. A special file named `.keep` is created at the *ref* root (full path: / *owner* / *repository* / *ref* / `.keep`). When the edit/build modifications are no longer required the `.keep` file may be deleted and the *ref* root will be garbage collected when not in use (i.e. when no files are open in it -- having a terminal window open with a current directory inside a *ref* root counts as an open file and the *ref* will not be garbage collected).
With release 2022 Beta1 HUBFS *ref* directories are now writable. This is implemented as a union file system that overlays a read-write local file system over the read-only Git content. This scheme allows files to be edited and builds to be performed. A special file named `.keep` is created at the *ref* root (full path: / *owner* / *repository* / *ref* / `.keep`). When the edit/build modifications are no longer required the `.keep` file may be deleted and the *ref* root will be garbage collected when not in use (i.e. when no files are open in it -- having a terminal window open with a current directory inside a *ref* root counts as an open file and the *ref* will not be garbage collected).

### Windows integration

Expand Down

0 comments on commit c2c5221

Please sign in to comment.