Jakob Reschke
Jakob Reschke
That the unrecorded files are among the unloadedArtifacts is as expected, because they are not somehow loaded into the image. A Key not found error is not expected, of course....
As a first step, please check whether the method I posted is the same in your images. :-)
Fetching the whole repository all the time is particularly nasty if you have a large file in the repository at some point in the history...
After this is resolved, we could optimize fetching by not unpacking the objects from the pack at all. The canonical Git just keeps the received pack file and creates an...
You mean that in addition to untracking a package (which removes it from Git upon the next commit) you also want to unload it?
You might have run into #179. To remove a package from Git, right-click it in the objects list (bottom right pane in the Git browser) of the lastet commit and...
Vocabulary and unloading issues are also relevant for #130. (Edit: ah, was already linked above...)
This and #256 has the challenge that the underlying patch of the save dialog would need its "left" side and the diffs updated correctly. The diff nodes must be updated...
This is obviously similar to #145, but I am not sure right now whether they are actually the same. This issue has the trees in commit and load dialogs in...
Gitless uses the Git stash and a special naming scheme for the stash messages to associate the stash entry with a branch. Since it uses something like `git stash apply`...