#43 (Re-)initialize a git repository as a gin repository

Open
opened 3 years ago by seharak · 2 comments

Hi,

Are there any ways to do it?

Recently Jiameng seems to have tried that, by running gin init in a git repository.

But then annex add did not work, leaving the large files as the "locally modified / untracked" state.

Checking files in directly in the repository was OK.

What is left to be done to get it work?

Hi, Are there any ways to do it? Recently Jiameng seems to have tried that, by running `gin init` in a git repository. But then `annex add` did not work, leaving the large files as the "locally modified / untracked" state. Checking files in directly in the repository was OK. What is left to be done to get it work?
Achilleas Koutsou commented 3 years ago
Owner

gin init should be enough. If you want to know what the command does in detail, this section of the help page describes the options it sets: https://gin.g-node.org/G-Node/Info/wiki/GIN+CLI+Usage+Tutorial#using-git-and-git-annex-directly. You can check them and see if it set everything up properly.

Something I forgot to ask before: Can you check the output of gin --version and post it here?

`gin init` should be enough. If you want to know what the command does in detail, this section of the help page describes the options it sets: https://gin.g-node.org/G-Node/Info/wiki/GIN+CLI+Usage+Tutorial#using-git-and-git-annex-directly. You can check them and see if it set everything up properly. Something I forgot to ask before: Can you check the output of `gin --version` and post it here?
Keisuke Sehara commented 3 years ago
Poster

Sorry for the delay in the response. Now I have checked that gin init is enough.

Probably there was an issue of checking in lots of files for the repository of interest.

Just in case, the version I was using was:

GIN command line client 1.12dev Build 001468 (b1b43ef061a7f0418f1d5c14ae60b49a92779b2d)
  git: 2.29.2.windows.2
  git-annex: 8.20201117-ge25d2c445
Sorry for the delay in the response. Now I have checked that `gin init` is enough. Probably there was an issue of checking in lots of files for the repository of interest. Just in case, the version I was using was: ``` GIN command line client 1.12dev Build 001468 (b1b43ef061a7f0418f1d5c14ae60b49a92779b2d) git: 2.29.2.windows.2 git-annex: 8.20201117-ge25d2c445 ```
Sign in to join this conversation.
No Milestone
No assignee
2 Participants
Loading...
Cancel
Save
There is no content yet.