matches must occur in the same line of text. For instance, let’s look for any lines that define a constant whose name contains either of the substrings “LINK” or “BUF_MAX”, specifically in an older version content of the diff they introduce. If, for example, we want to find out when the ZLIB_BUF_MAX constant was originally introduced, we can use the -S option (colloquially referred to as the Git “pickaxe” process 4GB at a time If we look at the diff of those commits, we can see that in ef49a7a the constant was introduced and in e01503b it was modified. If you need to be more specific, you can provide

matches must occur in the same line of text. For instance, let’s look for any lines that define a constant whose name contains either of the substrings “LINK” or “BUF_MAX”, specifically in an older version content of the diff they introduce. If, for example, we want to find out when the ZLIB_BUF_MAX constant was originally introduced, we can use the -S option (colloquially referred to as the Git “pickaxe” only process 4GB at a time If we look at the diff of those commits, we can see that in ef49a7a the constant was introduced and in e01503b it was modified. If you need to be more specific, you can provide

matches must occur in the same line of text. For instance, let’s look for any lines that define a constant whose name contains either of the substrings “LINK” or “BUF_MAX”, specifically in an older version content of the diff they introduce. If, for example, we want to find out when the ZLIB_BUF_MAX constant was originally introduced, we can use the -S option (colloquially referred to as the Git “pickaxe” process 4GB at a time If we look at the diff of those commits, we can see that in ef49a7a the constant was introduced and in e01503b it was modified. If you need to be more specific, you can provide