Hi Alex, the history is just work in progress, you should be able to load
any version from there, yes.
Yet I consider that a somehow advanced function, it will allow to load any
commit into your image.
So, wouldn't you prefer to load a branch or tag?
(For branches it is already supported, for tag
Le 26/08/2016 à 22:23, serge.stinckw...@gmail.com a écrit :
I got the same commit when I use Iceberg.
It's part of the gitfiletree setup (shared with filetree, and probably
libgit as well). We need to set a few properties inside the git repo,
and it has to be done as a commit to be recorded b
I got the same commit when I use Iceberg.
Envoyé de mon iPhone
> Le 26 août 2016 à 21:39, Alexandre Bergel a écrit :
>
> Hi!
>
> How can I load a version using Iceberg?
>
> I managed to open the history of a repo, but I cannot load a version.
> By the way, I see a commit with the comment ‘gi
Le vendredi 26 août 2016, Alexandre Bergel a
écrit :
>
> By the way, I see a commit with the comment ‘gitfiletree repository
> properties’. What is that? I have never made this commit.
>
it's made automatically when you first use the repo. Have a look at the
diff, there should be only a couple me
Hi!
How can I load a version using Iceberg?
I managed to open the history of a repo, but I cannot load a version.
By the way, I see a commit with the comment ‘gitfiletree repository
properties’. What is that? I have never made this commit.
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^
