Hi
It looks like the perl regular expression multiline mode does not work with
'git grep'
for example, something like
git grep -P '(?s)foo.*?bar"
will not match a file in the repo where it has something like
foo
bar
ie. split across two lines
Regards, Noel Grandin
--
To unsubscrib
On Wednesday, June 18, 2014, Jeff King wrote:
> Subject: ident_split: store begin/end pairs on their own struct
s/on/in/
> When we parse an ident line, we end up with several fields,
> each with a begin/end pointer into the buffer, like:
>
> const char *name_begin;
> const char *name_end;
>
On Wednesday, June 18, 2014, Jeff King wrote:
> Usually when we parse a commit, we read it line by line and
> handle each header in a single pass (e.g., in parse_commit
> and parse_commit_header). Sometimes, however, we only care
> about extracting a single header. Code in this situation is
> stu
Hi Junio,
On 06/20/2014 09:53 PM, Junio C Hamano wrote:
> Michael Haggerty writes:
>>> pick_one () {
>>> ff=--ff
>>> + extra_args=
>>> + while test $# -gt 0
>>> + do
>>> + case "$1" in
>>> + -n)
>>> + ff=
>>> + extra_args="$extra_
On 27/05/14 13:12, Ondrej Oprala wrote:
Hi, is there any way to display full tag names in gitk,
for tag names longer than 16 characters? The way 1.8.x did things?
The offending commit is 4399fe3 and reverting it restores my
preferred view, too (there was slight entanglement with
76d64ca which I
On Sun, Jun 22, 2014 at 05:22:32PM +0200, Matthieu Moy wrote:
> "Michael S. Tsirkin" writes:
>
> > Guess: auto-packing was started in background, did not
> > complete in time, and was restarted for the second time?
>
> Probably once for fetch, and another after rebase.
>
> > If true, some kind
Jens Lehmann wrote:
> Am 22.06.2014 16:09, schrieb Stephen Kelly:
>> Please show the same information (ie all commits newly reachable
>> from develop) in the submodule gitk output.
>
> This should not happen by default. If you have a feature branch based
> workflow, the merge is just what you wa
Am 22.06.2014 16:09, schrieb Stephen Kelly:
>
> Hello,
>
> boost.git, is using submodules.
>
> If I run gitk after a pull, there are some messages along the lines of
>
>
> Update preprocessor from develop.
>
> Submodule libs/preprocessor 9d2d1ff..1422fce:
> Merge branch 'master' i
"Michael S. Tsirkin" writes:
> Guess: auto-packing was started in background, did not
> complete in time, and was restarted for the second time?
Probably once for fetch, and another after rebase.
> If true, some kind of lock file would be useful
> to prevent this.
It is the case with recent ve
Hello,
boost.git, is using submodules.
If I run gitk after a pull, there are some messages along the lines of
Update preprocessor from develop.
Submodule libs/preprocessor 9d2d1ff..1422fce:
Merge branch 'master' into develop
That is, it shows only the merge.
If I then run
g
10 matches
Mail list logo
