Skip to content

Commit 725cf7b

Browse files
committed
Merge branch 'maint'
* maint: attr: plug minor memory leak request-pull: really disable pager Makes some cleanup/review in gittutorial Makefile: git.o depends on library headers git-submodule documentation: fix foreach example
2 parents 6167c13 + d4c9856 commit 725cf7b

File tree

6 files changed

+21
-17
lines changed

6 files changed

+21
-17
lines changed

Documentation/asciidoc.conf

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -17,6 +17,7 @@ caret=^
1717
startsb=[
1818
endsb=]
1919
tilde=~
20+
backtick=`
2021

2122
ifdef::backend-docbook[]
2223
[linkgit-inlinemacro]

Documentation/git-submodule.txt

Lines changed: 3 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -141,8 +141,9 @@ foreach::
141141
the processing to terminate. This can be overridden by adding '|| :'
142142
to the end of the command.
143143
+
144-
As an example, "git submodule foreach 'echo $path `git rev-parse HEAD`' will
145-
show the path and currently checked out commit for each submodule.
144+
As an example, +git submodule foreach \'echo $path {backtick}git
145+
rev-parse HEAD{backtick}'+ will show the path and currently checked out
146+
commit for each submodule.
146147

147148
sync::
148149
Synchronizes submodules' remote URL configuration setting

Documentation/gittutorial.txt

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -332,11 +332,11 @@ alice$ git log -p HEAD..FETCH_HEAD
332332
------------------------------------------------
333333

334334
This operation is safe even if Alice has uncommitted local changes.
335-
The range notation HEAD..FETCH_HEAD" means "show everything that is reachable
336-
from the FETCH_HEAD but exclude anything that is reachable from HEAD.
335+
The range notation "HEAD..FETCH_HEAD" means "show everything that is reachable
336+
from the FETCH_HEAD but exclude anything that is reachable from HEAD".
337337
Alice already knows everything that leads to her current state (HEAD),
338-
and reviewing what Bob has in his state (FETCH_HEAD) that she has not
339-
seen with this command
338+
and reviews what Bob has in his state (FETCH_HEAD) that she has not
339+
seen with this command.
340340

341341
If Alice wants to visualize what Bob did since their histories forked
342342
she can issue the following command:
@@ -375,9 +375,9 @@ it easier:
375375
alice$ git remote add bob /home/bob/myrepo
376376
------------------------------------------------
377377

378-
With this, Alice can perform the first part of the "pull" operation alone using the
379-
'git-fetch' command without merging them with her own branch,
380-
using:
378+
With this, Alice can perform the first part of the "pull" operation
379+
alone using the 'git-fetch' command without merging them with her own
380+
branch, using:
381381

382382
-------------------------------------
383383
alice$ git fetch bob
@@ -566,22 +566,22 @@ $ git log v2.5.. Makefile # commits since v2.5 which modify
566566

567567
You can also give 'git-log' a "range" of commits where the first is not
568568
necessarily an ancestor of the second; for example, if the tips of
569-
the branches "stable-release" and "master" diverged from a common
569+
the branches "stable" and "master" diverged from a common
570570
commit some time ago, then
571571

572572
-------------------------------------
573-
$ git log stable..experimental
573+
$ git log stable..master
574574
-------------------------------------
575575

576-
will list commits made in the experimental branch but not in the
576+
will list commits made in the master branch but not in the
577577
stable branch, while
578578

579579
-------------------------------------
580-
$ git log experimental..stable
580+
$ git log master..stable
581581
-------------------------------------
582582

583583
will show the list of commits made on the stable branch but not
584-
the experimental branch.
584+
the master branch.
585585

586586
The 'git-log' command has a weakness: it must present commits in a
587587
list. When the history has lines of development that diverged and

Makefile

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1464,7 +1464,7 @@ git-http-push$X: revision.o http.o http-push.o $(GITLIBS)
14641464
$(LIBS) $(CURL_LIBCURL) $(EXPAT_LIBEXPAT)
14651465

14661466
$(LIB_OBJS) $(BUILTIN_OBJS): $(LIB_H)
1467-
$(patsubst git-%$X,%.o,$(PROGRAMS)): $(LIB_H) $(wildcard */*.h)
1467+
$(patsubst git-%$X,%.o,$(PROGRAMS)) git.o: $(LIB_H) $(wildcard */*.h)
14681468
builtin-revert.o wt-status.o: wt-status.h
14691469

14701470
$(LIB_FILE): $(LIB_OBJS)

attr.c

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -555,6 +555,8 @@ static void prepare_attr_stack(const char *path, int dirlen)
555555
}
556556
}
557557

558+
strbuf_release(&pathbuf);
559+
558560
/*
559561
* Finally push the "info" one at the top of the stack.
560562
*/

git-request-pull.sh

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -42,8 +42,8 @@ if [ -z "$branch" ]; then
4242
status=1
4343
fi
4444

45-
PAGER=
46-
export PAGER
45+
GIT_PAGER=
46+
export GIT_PAGER
4747
echo "The following changes since commit $baserev:"
4848
git shortlog --max-count=1 $baserev | sed -e 's/^\(.\)/ \1/'
4949

0 commit comments

Comments
 (0)