Show 58 quoted lines
> On Mar 25, 2023, at 8:42 AM, Kristoffer Haugsbakk <code@khaugsbakk.name> wrote:
>
> On Sat, Mar 25, 2023, at 13:31, Mario Grgic wrote:
>> What happened instead? (Actual behavior)
>> Nothing is found, when in fact the search for term is present in the git
>> history
>>
>> What's different between what you expected and what actually happened?
>> git should print out the commit containing the search term.
>
> Weird. It works for me.
>
> $ mkdir test
> $ cd test
> $ git init
> $ [add file]
> $ # This was missing from the instructions
> $ git add --all
> $ git commit -m 'added test file'
> $ git log --all -p -G '\bmain\b'
> commit 56fbac5e12649c4de95071cc1872569d7c34055e (HEAD -> main)
> Author: Kristoffer Haugsbakk <code@khaugsbakk.name>
> Date: Sat Mar 25 13:33:51 2023 +0100
>
> added test file
>
> diff --git a/test.c b/test.c
> new file mode 100644
> index 0000000..0bffa6a
> --- /dev/null
> +++ b/test.c
> @@ -0,0 +1,5 @@
> +int main(int argc, const char *argv[])
> +{
> + return 0;
> +}
> +
>
> .
>
> [System Info]
> git version:
> git version 2.40.0
> cpu: x86_64
> no commit associated with this build
> sizeof-long: 8
> sizeof-size_t: 8
> shell-path: /bin/sh
> uname: Linux 5.4.0-144-generic #161~18.04.1-Ubuntu SMP Fri Feb 10 15:55:22 UTC 2023 x86_64
> compiler info: gnuc: 7.5
> libc info: glibc: 2.27
> $SHELL (typically, interactive shell): /bin/bash
>
>
> [Enabled Hooks]
>
> --
> Kristoffer Haugsbakk