The documentation for the feature 'snapshot' claimed
"This feature can be configured on a per-repository basis via
repository's `gitweb.blame` configuration variable"
Fixed to specify `gitweb.snapshot` as the variable name.
---
Documentation/gitweb.conf.txt | 2 +-
1 file changed, 1 insertion(+),
`**` special recursion powers only when used in
a path component by itself, otherwise it acts like `*`. So there's precedent
there.
dana
think of any reason i'd need that personally,
but then again i don't understand why these people are using `**` the way they
are in the first place.)
dana
ripgrep dev)
about this he said the same. I've CCed him on this message in case he has
anything to add.
dana
On 11 Oct 2018, at 05:19, dana wrote:
>git itself happily accepts these patterns, however, apparently treating the **
>like a single * without fnmatch(3)'s FNM_PATHNAME flag set (in other words, it
>matches / as a regular character, thus crossing directory boundaries).
Sorry f
hub.com/BurntSushi/ripgrep/issues/507
https://github.com/BurntSushi/ripgrep/issues/859
https://github.com/BurntSushi/ripgrep/issues/945
https://github.com/BurntSushi/ripgrep/issues/1080
https://github.com/BurntSushi/ripgrep/issues/1082
https://github.com/Microsoft/vscode/issues/24050
dana
#x27;t see that. That change does appear to solve the
same problem, so i'm happy to defer to it.
Thanks for looking!
dana
Fix a trivial white-space issue introduced by commit d48f97aa8
("rebase: reindent function git_rebase__interactive", 2018-03-23). This
affected the instructional comments displayed in the editor during an
interactive rebase.
Signed-off-by: dana
---
Sorry if i've done any of t
8 matches
Mail list logo
