Ævar Arnfjörð Bjarmason a8aea5db7a send-email: fix broken transferEncoding tests
I fixed a bug that had broken the reading of sendmail.transferEncoding
in 3494dfd3ee ("send-email: do defaults -> config -> getopt in that
order", 2019-05-09), but the test I added in that commit did nothing
to assert the bug had been fixed.

That issue originates in 8d81408435 ("git-send-email: add
--transfer-encoding option", 2014-11-25) which first added the
"sendemail.transferencoding=8bit".

That test has never done anything meaningful. It tested that the
"--transfer-encoding=8bit" option would turn on the 8bit
Transfer-Encoding, but that was the default at the time (and now). As
checking out 8d81408435 and editing the test to remove that option
will reveal, supplying it never did anything.

So when I copied it thinking it would work in 3494dfd3ee I copied a
previously broken test, although I was making sure it did the right
thing via da-hoc debugger inspection, so the bug was fixed.

So fix the test I added in 3494dfd3ee, as well as the long-standing
test added in 8d81408435. To test if we're actually setting the
Transfer-Encoding let's set it to 7bit, not 8bit, as 7bit will error
out on "email-using-8bit".

This means that we can remove the "sendemail.transferencoding=7bit
fails on 8bit data" test, since it was redundant, we now have other
tests that assert that that'll fail.

While I'm at it convert "git config <key> <value>" in the test setup
to just "-c <key>=<value>" on the command-line. Then we don't need to
cleanup after these tests, and there's no sense in asserting where
config values come from in these tests, we can take that as a given.

Signed-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2019-05-19 10:12:51 +09:00
2018-06-18 10:18:45 -07:00
2018-05-30 14:04:08 +09:00
2018-06-19 02:19:42 +09:00
2018-05-30 14:04:07 +09:00
2018-06-01 15:06:37 +09:00
2018-05-23 14:38:17 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 14:04:07 +09:00
2017-11-15 12:14:28 +09:00
2018-05-30 14:04:07 +09:00
2017-12-27 11:16:25 -08:00
2018-05-08 15:59:20 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 14:04:05 +09:00
2018-05-02 13:59:52 +09:00
2018-06-01 15:06:37 +09:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2018-05-30 14:04:07 +09:00
2018-06-13 12:50:46 -07:00
2018-05-30 14:04:08 +09:00
2018-05-08 15:59:17 +09:00
2018-05-08 15:59:27 +09:00
2018-06-01 15:06:37 +09:00
2018-03-15 12:01:09 -07:00
2018-02-13 13:39:04 -08:00
2018-05-08 15:59:22 +09:00
2018-05-08 15:59:22 +09:00
2017-12-08 09:16:27 -08:00
2017-12-08 09:16:27 -08:00
2018-05-30 14:04:10 +09:00
2018-02-15 14:55:43 -08:00
2018-06-18 11:23:22 -07:00
2018-05-30 14:04:10 +09:00
2018-03-14 09:23:50 -07:00
2018-05-08 15:59:34 +09:00
2018-05-08 15:59:17 +09:00
2018-05-08 15:59:16 +09:00
2018-05-21 23:55:12 -04:00
2018-05-08 15:59:34 +09:00
2018-06-18 10:18:41 -07:00
2018-06-21 10:00:06 -07:00
2018-06-01 15:06:37 +09:00
2017-11-21 14:05:30 +09:00
2018-06-01 15:06:37 +09:00
2018-05-08 15:59:16 +09:00
2018-04-11 13:09:55 +09:00
2018-05-30 21:51:28 +09:00
2018-05-23 14:38:13 +09:00
2017-09-06 17:19:54 +09:00
2018-06-18 11:23:24 -07:00
2018-05-30 14:04:07 +09:00
2018-05-23 14:38:16 +09:00
2017-12-27 12:28:06 -08:00
2017-11-22 14:11:56 +09:00
2018-05-30 14:04:07 +09:00
2018-02-02 11:28:41 -08:00
2018-05-30 14:04:10 +09:00
2018-06-01 15:06:37 +09:00
2018-05-29 17:10:05 +09:00
2017-12-13 11:14:25 -08:00
2018-05-30 14:04:07 +09:00
2018-05-23 14:38:13 +09:00
2017-12-12 10:41:15 -08:00
2017-12-19 11:33:55 -08:00
2018-01-16 12:16:54 -08:00
2018-05-30 14:04:10 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 21:51:28 +09:00
2018-05-08 15:59:21 +09:00
2018-06-04 21:39:50 +09:00
2018-05-22 14:28:26 +09:00
2018-05-30 14:04:05 +09:00
2018-05-30 14:04:10 +09:00
2018-03-15 12:01:08 -07:00
2018-05-30 14:04:11 +09:00
2018-05-30 14:04:07 +09:00
2018-06-01 15:06:37 +09:00
2018-04-24 11:12:32 +09:00
2018-05-30 14:04:07 +09:00
2018-05-30 14:04:10 +09:00
2018-05-30 14:04:10 +09:00
2018-03-30 12:49:57 -07:00
2018-03-30 12:49:57 -07:00
2017-08-26 22:55:04 -07:00
2018-05-23 14:38:13 +09:00
2018-05-30 21:51:28 +09:00
2018-05-29 17:10:05 +09:00
2018-05-29 17:10:05 +09:00
2018-05-23 14:38:13 +09:00
2018-05-30 14:04:10 +09:00

Git - fast, scalable, distributed revision control system

Git is a fast, scalable, distributed revision control system with an unusually rich command set that provides both high-level operations and full access to internals.

Git is an Open Source project covered by the GNU General Public License version 2 (some parts of it are under different licenses, compatible with the GPLv2). It was originally written by Linus Torvalds with help of a group of hackers around the net.

Please read the file INSTALL for installation instructions.

Many Git online resources are accessible from https://git-scm.com/ including full documentation and Git related tools.

See Documentation/gittutorial.txt to get started, then see Documentation/giteveryday.txt for a useful minimum set of commands, and Documentation/git-.txt for documentation of each command. If git has been correctly installed, then the tutorial can also be read with man gittutorial or git help tutorial, and the documentation of each command with man git-<commandname> or git help <commandname>.

CVS users may also want to read Documentation/gitcvs-migration.txt (man gitcvs-migration or git help cvs-migration if git is installed).

The user discussion and development of Git take place on the Git mailing list -- everyone is welcome to post bug reports, feature requests, comments and patches to git@vger.kernel.org (read Documentation/SubmittingPatches for instructions on patch submission). To subscribe to the list, send an email with just "subscribe git" in the body to majordomo@vger.kernel.org. The mailing list archives are available at https://public-inbox.org/git/, http://marc.info/?l=git and other archival sites.

Issues which are security relevant should be disclosed privately to the Git Security mailing list git-security@googlegroups.com.

The maintainer frequently sends the "What's cooking" reports that list the current status of various development topics to the mailing list. The discussion following them give a good reference for project status, development direction and remaining tasks.

The name "git" was given by Linus Torvalds when he wrote the very first version. He described the tool as "the stupid content tracker" and the name as (depending on your mood):

  • random three-letter combination that is pronounceable, and not actually used by any common UNIX command. The fact that it is a mispronunciation of "get" may or may not be relevant.
  • stupid. contemptible and despicable. simple. Take your pick from the dictionary of slang.
  • "global information tracker": you're in a good mood, and it actually works for you. Angels sing, and a light suddenly fills the room.
  • "goddamn idiotic truckload of sh*t": when it breaks
Description
No description provided
Readme 279 MiB
Languages
C 50.5%
Shell 38.7%
Perl 4.5%
Tcl 3.2%
Python 0.8%
Other 2.1%