<feed xmlns='http://www.w3.org/2005/Atom'>
<title>git/t/t7502-commit.sh, branch v1.6.3</title>
<subtitle>Mirror of https://git.kernel.org/pub/scm/git/git.git/
</subtitle>
<id>https://git.shady.money/git/atom?h=v1.6.3</id>
<link rel='self' href='https://git.shady.money/git/atom?h=v1.6.3'/>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/'/>
<updated>2009-03-25T20:25:57Z</updated>
<entry>
<title>t7502-commit: Skip SIGTERM test on Windows</title>
<updated>2009-03-25T20:25:57Z</updated>
<author>
<name>Johannes Sixt</name>
<email>j6t@kdbg.org</email>
</author>
<published>2009-03-25T12:21:15Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=fb9a2beab2002894fb970cba4e32ebb1c41176b2'/>
<id>urn:sha1:fb9a2beab2002894fb970cba4e32ebb1c41176b2</id>
<content type='text'>
The implementation of exec on Windows is just a rough approximation of the
POSIX behavior. In particular, no real process "overlay" happens (a new
process is spawned instead and the parent process waits until the child
terminates). In particular, the process ID cannot be taken by the exec'd
process. But there is one test in t7502-commit.sh that depends on this.
We have to skip it on Windows.

Signed-off-by: Johannes Sixt &lt;j6t@kdbg.org&gt;
</content>
</entry>
<entry>
<title>wt-status: load diff ui config</title>
<updated>2008-10-26T21:09:48Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2008-10-26T04:49:35Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=4f672ad6c77bfe73cc5dd4b240fd42303d101d2a'/>
<id>urn:sha1:4f672ad6c77bfe73cc5dd4b240fd42303d101d2a</id>
<content type='text'>
When "git status -v" shows a diff, we did not respect the
user's usual diff preferences at all. Loading just
git_diff_basic_config would give us things like rename
limits and diff drivers. But it makes even more sense to
load git_diff_ui_config, which gives us colorization if the
user has requested it.

Note that we need to take special care to cancel
colorization when writing to the commit template file, as
described in the code comments.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Compact commit template message</title>
<updated>2008-07-31T18:20:13Z</updated>
<author>
<name>Jeff King</name>
<email>peff@peff.net</email>
</author>
<published>2008-07-31T07:36:09Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=fdc7c81111a2ca8d97b8b45e260d7a4e737c8766'/>
<id>urn:sha1:fdc7c81111a2ca8d97b8b45e260d7a4e737c8766</id>
<content type='text'>
We recently let the user know explicitly that an empty
commit message will abort the commit. However, this adds yet
another line to the template; let's rephrase and re-wrap so
that this fits back on two lines.

This patch also makes the "fatal: empty commit message?"
warning a bit less scary, since this is now a "feature"
instead of an error. However, we retain the non-zero exit
status to indicate to callers that nothing was committed.

Signed-off-by: Jeff King &lt;peff@peff.net&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>Advertise the ability to abort a commit</title>
<updated>2008-07-30T07:00:02Z</updated>
<author>
<name>Anders Melchiorsen</name>
<email>mail@cup.kalibalik.dk</email>
</author>
<published>2008-07-29T20:12:22Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=bd2574ca69331d33429f8806ce189b2941e490e7'/>
<id>urn:sha1:bd2574ca69331d33429f8806ce189b2941e490e7</id>
<content type='text'>
This treats aborting a commit more like a feature.

Signed-off-by: Anders Melchiorsen &lt;mail@cup.kalibalik.dk&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>t7502-commit.sh: rearrange test to make more portable</title>
<updated>2008-07-23T18:36:31Z</updated>
<author>
<name>Brandon Casey</name>
<email>casey@nrlssc.navy.mil</email>
</author>
<published>2008-07-22T21:21:10Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=09b78bc1fc4e525bc68fa0ce76521457717fe675'/>
<id>urn:sha1:09b78bc1fc4e525bc68fa0ce76521457717fe675</id>
<content type='text'>
Some shells have problems with one-shot environment variable export
and function calls. The sequence is rearranged to avoid the one-shot
and to allow the test script to be linked together with '&amp;&amp;'.

Signed-off-by: Brandon Casey &lt;casey@nrlssc.navy.mil&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>t7502-commit.sh: test_must_fail doesn't work with inline environment variables</title>
<updated>2008-06-19T23:07:06Z</updated>
<author>
<name>Brandon Casey</name>
<email>casey@nrlssc.navy.mil</email>
</author>
<published>2008-06-19T17:32:02Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=e2007832552ccea9befed9003580c494f09e666e'/>
<id>urn:sha1:e2007832552ccea9befed9003580c494f09e666e</id>
<content type='text'>
When the arguments to test_must_fail() begin with a variable assignment,
test_must_fail() attempts to execute the variable assignment as a command.
This fails, and so test_must_fail returns with a successful status value
without running the command it was intended to test.

For example, the following script:

	#!/bin/sh
	test_must_fail () {
		"$@"
		test $? -gt 0 -a $? -le 129
	}
	foo='wo adrian'
	test_must_fail foo='yo adrian' sh -c 'echo foo: $foo'

always exits zero and prints the message:

	test.sh: line 3: foo=yo adrian: command not found

Test 16 calls test_must_fail in such a way and therefore has not been
testing whether git 'do[es] not fire editor in the presence of conflicts'.

A workaround is to set and export the variable in a normal way, not
using one-shot notation.  Because this would affect the remainder of
the process, the test is done inside a subshell.

Signed-off-by: Brandon Casey &lt;casey@nrlssc.navy.mil&gt;
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>t7502: honor SHELL_PATH</title>
<updated>2008-06-04T19:11:59Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-06-04T19:10:01Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=de5825cc829a5d535de726eb7e5af45c0a3b88ce'/>
<id>urn:sha1:de5825cc829a5d535de726eb7e5af45c0a3b88ce</id>
<content type='text'>
Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>t7502: tighten loosely written test sequence</title>
<updated>2008-06-04T01:13:33Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-06-04T01:10:08Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=a3c91e088ead7c47f43efe8da625d190dcef1001'/>
<id>urn:sha1:a3c91e088ead7c47f43efe8da625d190dcef1001</id>
<content type='text'>
We would like to catch breakage at any step in the sequence.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>t7502: do not globally unset GIT_COMMITTER_* environment variables</title>
<updated>2008-06-04T01:08:08Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-06-04T01:08:08Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=7845944c64de11d87e3b33ed7fa0a0a4b00fa435'/>
<id>urn:sha1:7845944c64de11d87e3b33ed7fa0a0a4b00fa435</id>
<content type='text'>
One particular test wants to check the behaviour of the command
when these variables are not set, but the later tests should have
the reliable committer identity for repeatable tests.

Move the "unset" of the variables inside a subshell in the test
that wants to unset them.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
<entry>
<title>commit: drop duplicated parents</title>
<updated>2008-06-03T06:55:57Z</updated>
<author>
<name>Junio C Hamano</name>
<email>gitster@pobox.com</email>
</author>
<published>2008-06-03T05:17:42Z</published>
<link rel='alternate' type='text/html' href='https://git.shady.money/git/commit/?id=67bfc030d7b27c007853776e8028598bdfa2cae0'/>
<id>urn:sha1:67bfc030d7b27c007853776e8028598bdfa2cae0</id>
<content type='text'>
The scripted version of git-commit internally used git-commit-tree which
omitted duplicated parents given from the command line.  This prevented a
nonsensical octopus merge from getting created even when you said "git
merge A B" while you are already on branch A.

However, when git-commit was rewritten in C, this sanity check was lost.
This resurrects it.

Signed-off-by: Junio C Hamano &lt;gitster@pobox.com&gt;
</content>
</entry>
</feed>
