Version 1.12

Version 1.12

Changes

• Adding a script that, when run, sets up the user's %path% to be able to run gin from anywhere on Windows.
• Adding a new wrapper script for running gin commands on Windows. The new script (gin.bat) acts as the main entrypoint for commands on Windows. It sets up a temporary (local) path where the gin-cli can find all necessary binaries (git, git-annex, etc.) and then runs the command with the user's arguments. If this script is in the user's %path%, the rest of the software doesn't need to be. The bundled binaries take precedence over any existing binaries with the same name in the %path% since the temporary paths are prepended before calling gin.exe. The set-global.bat file has been adjusted to add only the path with the gin.bat in it. It also prompts the user to clean their path of any existing GIN CLI directories, if any are detected. This is better done manually, since parsing and editing the path is too error prone.
• When fetching git config keys, only use keys from the local git configuration and never include a global config.

Relevant PRs

• #290 Windows global cmd
• #301 Less intrusive Windows paths
• #307 Use only local git config keys

Version 1.11

Changes

• Updated bundled git-annex for Windows packages to 8.20200330.
• Added bat script in Windows bundles that adds the GIN extraction path to the user's run path to make it globally available outside the GIN shell.

Version 1.10

Version 1.10

Changes

• When adding files to the annex, a new message is displayed at the end of the add step: "Writing filename metadata". This step was performed before but did not produce any output.
• Warns when a repository is using an old format version and offers instructions to upgrade.
• Files involved in a merge conflict are no longer listed in the error message. This is a limitation with the underlying Git-annex messages.

Bug fixes

• Fixes client hanging after adding a large number of files.

Relevant PRs

• #268: Fix for add command seemingly hanging at the end
• #279: [annex] Print progress of metadata writing
• #271: Annex upgrade notice
• #275: Error message update for new annex

Version 1.9

Version 1.9

Changes

• Default address for GIN server is now gin.g-node.org. The old web address, web.gin.g-node.org still works but will be unavailable in the future.
• 64-bit version for Windows now available. This version is necessary for managing files larger than 4 GiB.

Relevant PRs

• #266: Changing web addresses to gin.g-node.org
• #267: Package 64-bit version for Windows

Version 1.8

Version 1.8

Changes

• Added Default field to gin servers JSON output.

Relevant PRs

• #262: [serverscmd] Include "default" in servers JSON output

Version 1.7

Changes

• Git annex v7 mode: With this version, new repositories and local clones are initialised in git-annex v7 mode. This brings several changes in the behaviour of file locking:
  • Files are added unlocked by default.
  • Locking a file is a persistent status change that can be committed to the repository and will affect other clones.
  • Locked files are not usable on Windows (not even for reading) and need to be unlocked.
  • If no locking or unlocking is performed, the behaviour is is identical across all platforms.
• New command: gin sync
  • Synchronises changes bidirectionally between remote repositories and the local clone.
  • Content can be synchronised at the same time with the --content flag.
  • Using the --content flag will download all data in the repository.
• gin version --copy-to behaviour changes:
  • Files can now be checked out from older versions to any location, i.e., the destination directory does not need to be under the repository root.
  • Checked out files (the old versions) are not added to the repository.
  • Annexed content of checked out files is automatically downloaded.
• Custom commit messages: Users can now specify a custom commit message when performing a gin commit by specifying the --message flag (-m for short).
• Better handling of merge conflicts.
• gin ls file listings are colour coded. Synced files are green, pointer files without content are cyan, modified files are yellow/orange, removed files are red.
• gin ls prints a summary with file counts for each status at the bottom of the output.
• JSON output has been added (--json flag) to the info, keys, servers, and remotes commands.
• A message is always printed when there is "Nothing to do".
• Output is more consistent across all file operations.

Bug fixes

• Fixed bugs with colours in Windows terminals.
• Fixed bug where the log would not be properly trimmed on Windows.
• Fixed bug where gin version --copy-to would fail on Windows.

Relevant PRs

• #237: Windows colours
• #241: Fix for adding annexed content to git on Windows
• #242: Count only T (typechange) files
• #244: Log trim fix
• #247: More consistent file operation messages
• #248: Small Changes to Verbose flag
• #250: Windows fixes and annex v7
• #253: Support custom commit messages
• #254: Changes to 'gin version' command behaviour
• #256: LScmd enhancement
• #257: Bugfix for 'git cat-file' on Windows (for 'gin version --copy-to')
• #258: gin ls summary
• #260: Add JSON output to info, keys, servers, and remotes commands

Version 1.6

Bug fixes

• Fixed bug where commands repos and repoinfo would still prompt for login when called with --json flag and the user was not logged in. Commands invoked with the --json flag should never prompt for any input.
• Fixed colour output in Windows.
• Fixed bug where annexed content would also be added to git on Windows.

Relevant PRs

• #236: Don't prompt for login with --json
• #237: Windows colours
• #241: Fix for adding annexed content to git on Windows

Version 1.5

Bug fixes

• Fixed bug where the annex initialisation on Windows would fail due to the repository working in direct mode.
• Fixed minor bug in the error field for JSON output.

Relevant PRs

• #232: Use git-annex-sync to create empty init commit

Version 1.4

• Repackaging for git-annex version for Windows

Version 1.3

Bug fixes

• Fixed bug when committing or uploading multiple large files. Some files would fail to be added to the annex resulting in them being added to git.

Internal changes

• Repositories are explicitly set to annex version 5 mode on initialisation.

Relevant PRs

• #229: Force v5 repos
• #231: Fix filename metadata write