# orderedItems[].object.content
@abbe98 I don't know. I guess it's related to origin/HEAD.

# orderedItems[].object.contentMap.en
@abbe98 I don't know. I guess it's related to origin/HEAD.

# orderedItems[].object.content
@abbe98 I assume there is a simpler way but this seems to work

```sh
git worktree add "$(git config --get init.defaultBranch || echo master)" ../main-branch
```

# orderedItems[].object.contentMap.en
@abbe98 I assume there is a simpler way but this seems to work

```sh
git worktree add "$(git config --get init.defaultBranch || echo master)" ../main-branch
```

# orderedItems[].object.content
@loevenbruck La parole c'est environ 150 mots par minutes (et la télé/radio, c'est plutôt la fourchette basse). Donc 10 secondes c'est 25 mots. Autrement dit un demi paragraphe...

# orderedItems[].object.contentMap.fr
@loevenbruck La parole c'est environ 150 mots par minutes (et la télé/radio, c'est plutôt la fourchette basse). Donc 10 secondes c'est 25 mots. Autrement dit un demi paragraphe...

# orderedItems[].object.content
@ellouis En plus du mérinos comme les autres te conseillent, je ferais comme pour ma serviette et je le mettrai à sécher/aérer sur mon vélo

# orderedItems[].object.contentMap.fr
@ellouis En plus du mérinos comme les autres te conseillent, je ferais comme pour ma serviette et je le mettrai à sécher/aérer sur mon vélo

# orderedItems[].object.content
@PacoVelobs @fabi1cazenave @flomaraninchi @taratatach @gill @abkgrenoble j'avais déjà répondu positif ! Je regarde le mot dièse "grenoble" et quelqu'un a posté dessus

# orderedItems[].object.contentMap.fr
@PacoVelobs @fabi1cazenave @flomaraninchi @taratatach @gill @abkgrenoble j'avais déjà répondu positif ! Je regarde le mot dièse "grenoble" et quelqu'un a posté dessus

# orderedItems[].object.content
@abbe98 If I plan to use multiple worktrees, I usually create a bare clone, but except that I do the same as you.

# orderedItems[].object.contentMap.en
@abbe98 If I plan to use multiple worktrees, I usually create a bare clone, but except that I do the same as you.

# orderedItems[].object.content
Neat, I just realized its possible to see all the code of all modified functions in a commit (the short option is -W)

git show --function-context $some_commit

#git

# orderedItems[].object.contentMap.en
Neat, I just realized its possible to see all the code of all modified functions in a commit (the short option is -W)

git show --function-context $some_commit

#git

# orderedItems[].object.content
I was sure I remove some functionality in a function I wrote a few month ago, but finally I had to reintroduced it. All I had to do was to look at the history of this function

git log -L :func_name:path/to/file

And I was able to easily identify the commit that removed the code, a simple `git revert` and voilà, it’s done!

I am using the console, but I assume that IDE have a way to do the same, and if they don’t it’s a missed opportunity. That was very handy!

#git #gitlog

# orderedItems[].object.contentMap.en
I was sure I remove some functionality in a function I wrote a few month ago, but finally I had to reintroduced it. All I had to do was to look at the history of this function

git log -L :func_name:path/to/file

And I was able to easily identify the commit that removed the code, a simple `git revert` and voilà, it’s done!

I am using the console, but I assume that IDE have a way to do the same, and if they don’t it’s a missed opportunity. That was very handy!

#git #gitlog

# orderedItems[].object.content
Just added a few birds to my entrance door. I'm very pleased with the result.

#woodworking #scrollsaw #scrollsawart #birds

# orderedItems[].object.contentMap.en
Just added a few birds to my entrance door. I'm very pleased with the result.

#woodworking #scrollsaw #scrollsawart #birds

# orderedItems[].object.attachment[].name
3 birds and a butterfly that I made with wood with my scrollsaw, stick on my entrance door.

# orderedItems[].object.content
@ClickHouseCI In which concrete situation do you use the reflog?

For me it's exclusively to find back orphans. This is why I prefer to use the graph view. I find it easier to find the commit I lost than in the reflog where orphans can't easily be identified.

Said otherwise, I'm more interested to answer the question "which orphans did I lost" than "what command that move HEAD did I run".

It seems that you use the reflog in other situations, I'm curious in which one.

# orderedItems[].object.contentMap.en
@ClickHouseCI In which concrete situation do you use the reflog?

For me it's exclusively to find back orphans. This is why I prefer to use the graph view. I find it easier to find the commit I lost than in the reflog where orphans can't easily be identified.

Said otherwise, I'm more interested to answer the question "which orphans did I lost" than "what command that move HEAD did I run".

It seems that you use the reflog in other situations, I'm curious in which one.

# orderedItems[].object.content
@ClickHouseCI @maikel Orphans commits don't have reference pointing to them or one of there descendant, which include local branches, tags, but also distant branches (origin/*).

There is no differences between your graph if you do `git log --graph --reflog` and `git log --graph --all`. If you had orphans, you would see more commits with --rebase.

Such situation happens when rebasing or reseting a local-only branch leaving orphaned commits behind, which is when I find the reflog useful.

# orderedItems[].object.contentMap.en
@ClickHouseCI @maikel Orphans commits don't have reference pointing to them or one of there descendant, which include local branches, tags, but also distant branches (origin/*).

There is no differences between your graph if you do `git log --graph --reflog` and `git log --graph --all`. If you had orphans, you would see more commits with --rebase.

Such situation happens when rebasing or reseting a local-only branch leaving orphaned commits behind, which is when I find the reflog useful.

# orderedItems[].object.content
@ClickHouseCI @maikel I never had to use the reflog on non-orphans commits that I want to access. Your image doesn't have any orphans which is why I did not realised there where rebase in it.

# orderedItems[].object.contentMap.en
@ClickHouseCI @maikel I never had to use the reflog on non-orphans commits that I want to access. Your image doesn't have any orphans which is why I did not realised there where rebase in it.

# orderedItems[].object.content
@ClickHouseCI @maikel Just look at the output of `git reflog` and `git log --graph --reflog` after a rebase to see what I mean.

# orderedItems[].object.contentMap.en
@ClickHouseCI @maikel Just look at the output of `git reflog` and `git log --graph --reflog` after a rebase to see what I mean.

# orderedItems[].object.content
@ClickHouseCI @maikel If you do a rebase, do some stuff, then realise you want to undo the rebase the output of `git reflog` is basically unusable because the commit you want (the tip of the branch before the rebase) has the exact same summary as the commit in your branch (the one after the rebase) which is extra confusing. But in the graph version, the old commit is the tip of an orphaned part of the tree (no branch).

# orderedItems[].object.contentMap.en
@ClickHouseCI @maikel If you do a rebase, do some stuff, then realise you want to undo the rebase the output of `git reflog` is basically unusable because the commit you want (the tip of the branch before the rebase) has the exact same summary as the commit in your branch (the one after the rebase) which is extra confusing. But in the graph version, the old commit is the tip of an orphaned part of the tree (no branch).

# orderedItems[].object.content
@ClickHouseCI @maikel The issue is that the output of the reflog you show is not representative of when I need to use the reflog.

# orderedItems[].object.contentMap.en
@ClickHouseCI @maikel The issue is that the output of the reflog you show is not representative of when I need to use the reflog.