<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/contrib/examples, branch v2.8.2</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v2.8.2</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v2.8.2'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2015-12-27T23:33:13Z</updated>
<entry>
<title>contrib/examples/git-revert.sh: use the $( ... ) construct for command substitution</title>
<updated>2015-12-27T23:33:13Z</updated>
<author>
<name>Elia Pinto</name>
<email>gitter.spiros@gmail.com</email>
</author>
<published>2015-12-22T14:10:27Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=bc32bacc72078b92b9e9f02acec63ccc28564a01'/>
<id>urn:sha1:bc32bacc72078b92b9e9f02acec63ccc28564a01</id>
<content type='text'>
The Git CodingGuidelines prefer the $(...) construct for command
substitution instead of using the backquotes `...`.

The backquoted form is the traditional method for command
substitution, and is supported by POSIX.  However, all but the
simplest uses become complicated quickly.  In particular, embedded
command substitutions and/or the use of double quotes require
careful escaping with the backslash character.

The patch was generated by:

for _f in $(find . -name "*.sh")
do
	perl -i -pe 'BEGIN{undef $/;} s/`(.+?)`/\$(\1)/smg'  "${_f}"
done

and then carefully proof-read.

Signed-off-by: Elia Pinto &lt;gitter.spiros@gmail.com&gt;
Reviewed-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>contrib/examples/git-repack.sh: use the $( ... ) construct for command substitution</title>
<updated>2015-12-27T23:33:13Z</updated>
<author>
<name>Elia Pinto</name>
<email>gitter.spiros@gmail.com</email>
</author>
<published>2015-12-22T14:10:26Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=6ccca67a74807c14970d08efd635bdef9af6c17c'/>
<id>urn:sha1:6ccca67a74807c14970d08efd635bdef9af6c17c</id>
<content type='text'>
The Git CodingGuidelines prefer the $(...) construct for command
substitution instead of using the backquotes `...`.

The backquoted form is the traditional method for command
substitution, and is supported by POSIX.  However, all but the
simplest uses become complicated quickly.  In particular, embedded
command substitutions and/or the use of double quotes require
careful escaping with the backslash character.

The patch was generated by:

for _f in $(find . -name "*.sh")
do
	perl -i -pe 'BEGIN{undef $/;} s/`(.+?)`/\$(\1)/smg'  "${_f}"
done

and then carefully proof-read.

Signed-off-by: Elia Pinto &lt;gitter.spiros@gmail.com&gt;
Reviewed-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>contrib/examples/git-merge.sh: use the $( ... ) construct for command substitution</title>
<updated>2015-12-27T23:33:13Z</updated>
<author>
<name>Elia Pinto</name>
<email>gitter.spiros@gmail.com</email>
</author>
<published>2015-12-22T14:10:25Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=1a3655264ebb238692b3666afe338e094fdb3609'/>
<id>urn:sha1:1a3655264ebb238692b3666afe338e094fdb3609</id>
<content type='text'>
The Git CodingGuidelines prefer the $(...) construct for command
substitution instead of using the backquotes `...`.

The backquoted form is the traditional method for command
substitution, and is supported by POSIX.  However, all but the
simplest uses become complicated quickly.  In particular, embedded
command substitutions and/or the use of double quotes require
careful escaping with the backslash character.

The patch was generated by:

for _f in $(find . -name "*.sh")
do
	perl -i -pe 'BEGIN{undef $/;} s/`(.+?)`/\$(\1)/smg'  "${_f}"
done

and then carefully proof-read.

Signed-off-by: Elia Pinto &lt;gitter.spiros@gmail.com&gt;
Reviewed-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>contrib/examples/git-fetch.sh: use the $( ... ) construct for command substitution</title>
<updated>2015-12-27T23:33:13Z</updated>
<author>
<name>Elia Pinto</name>
<email>gitter.spiros@gmail.com</email>
</author>
<published>2015-12-22T14:10:24Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=cc301d7e5193801208588cbd54cf1af91b6f7a00'/>
<id>urn:sha1:cc301d7e5193801208588cbd54cf1af91b6f7a00</id>
<content type='text'>
The Git CodingGuidelines prefer the $(...) construct for command
substitution instead of using the backquotes `...`.

The backquoted form is the traditional method for command
substitution, and is supported by POSIX.  However, all but the
simplest uses become complicated quickly.  In particular, embedded
command substitutions and/or the use of double quotes require
careful escaping with the backslash character.

The patch was generated by:

for _f in $(find . -name "*.sh")
do
	perl -i -pe 'BEGIN{undef $/;} s/`(.+?)`/\$(\1)/smg'  "${_f}"
done

and then carefully proof-read.

Signed-off-by: Elia Pinto &lt;gitter.spiros@gmail.com&gt;
Reviewed-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>contrib/examples/git-commit.sh: use the $( ... ) construct for command substitution</title>
<updated>2015-12-27T23:33:13Z</updated>
<author>
<name>Elia Pinto</name>
<email>gitter.spiros@gmail.com</email>
</author>
<published>2015-12-22T14:10:23Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a22c9e8d9e29277f51b77aff8d0eee3945577e72'/>
<id>urn:sha1:a22c9e8d9e29277f51b77aff8d0eee3945577e72</id>
<content type='text'>
The Git CodingGuidelines prefer the $(...) construct for command
substitution instead of using the backquotes `...`.

The backquoted form is the traditional method for command
substitution, and is supported by POSIX.  However, all but the
simplest uses become complicated quickly.  In particular, embedded
command substitutions and/or the use of double quotes require
careful escaping with the backslash character.

The patch was generated by:

for _f in $(find . -name "*.sh")
do
	perl -i -pe 'BEGIN{undef $/;} s/`(.+?)`/\$(\1)/smg'  "${_f}"
done

and then carefully proof-read.

Signed-off-by: Elia Pinto &lt;gitter.spiros@gmail.com&gt;
Reviewed-by: Jonathan Nieder &lt;jrnieder@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'pt/pull-builtin'</title>
<updated>2015-10-14T21:30:21Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-10-14T21:30:20Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=1311587d96e0bff17a34dc9bb9ad27c3abdacdbc'/>
<id>urn:sha1:1311587d96e0bff17a34dc9bb9ad27c3abdacdbc</id>
<content type='text'>
* pt/pull-builtin:
  merge: grammofix in please-commit-before-merge message
</content>
</entry>
<entry>
<title>merge: grammofix in please-commit-before-merge message</title>
<updated>2015-10-02T21:29:56Z</updated>
<author>
<name>Alex Henrie</name>
<email>alexhenrie24@gmail.com</email>
</author>
<published>2015-10-02T04:25:33Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=b7447679e84ed973430ab19fce87f56857b83068'/>
<id>urn:sha1:b7447679e84ed973430ab19fce87f56857b83068</id>
<content type='text'>
Signed-off-by: Alex Henrie &lt;alexhenrie24@gmail.com&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Merge branch 'js/maint-am-skip-performance-regression'</title>
<updated>2015-09-14T21:59:13Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-09-14T21:59:07Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=cf2094ca6349fe8cfe0f327e36ea386ad8ac98db'/>
<id>urn:sha1:cf2094ca6349fe8cfe0f327e36ea386ad8ac98db</id>
<content type='text'>
Recent versions of scripted "git am" has a performance regression in
"git am --skip" codepath, which no longer exists in the built-in
version on the 'master' front.  Fix the regression in the last
scripted version that appear in 2.5.x maintenance track and older.

* js/maint-am-skip-performance-regression:
  am --skip/--abort: merge HEAD/ORIG_HEAD tree into index
</content>
</entry>
<entry>
<title>Sync with maint</title>
<updated>2015-08-25T23:09:30Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-08-25T23:09:30Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=33f2c4ff7b9ac02cd9010d504e847b912b35baf6'/>
<id>urn:sha1:33f2c4ff7b9ac02cd9010d504e847b912b35baf6</id>
<content type='text'>
* maint:
  pull: pass upload_pack only when it was given
</content>
</entry>
<entry>
<title>Merge branch 'jk/git-path'</title>
<updated>2015-08-19T21:48:56Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2015-08-19T21:48:56Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=8c9155e031869293b99531a25b585e49f74beaba'/>
<id>urn:sha1:8c9155e031869293b99531a25b585e49f74beaba</id>
<content type='text'>
git_path() and mkpath() are handy helper functions but it is easy
to misuse, as the callers need to be careful to keep the number of
active results below 4.  Their uses have been reduced.

* jk/git-path:
  memoize common git-path "constant" files
  get_repo_path: refactor path-allocation
  find_hook: keep our own static buffer
  refs.c: remove_empty_directories can take a strbuf
  refs.c: avoid git_path assignment in lock_ref_sha1_basic
  refs.c: avoid repeated git_path calls in rename_tmp_log
  refs.c: simplify strbufs in reflog setup and writing
  path.c: drop git_path_submodule
  refs.c: remove extra git_path calls from read_loose_refs
  remote.c: drop extraneous local variable from migrate_file
  prefer mkpathdup to mkpath in assignments
  prefer git_pathdup to git_path in some possibly-dangerous cases
  add_to_alternates_file: don't add duplicate entries
  t5700: modernize style
  cache.h: complete set of git_path_submodule helpers
  cache.h: clarify documentation for git_path, et al
</content>
</entry>
</feed>
