1
0
mirror of https://github.com/git/git.git synced 2025-04-13 11:22:40 +00:00
Stephen Boyd 21802cd328 send-email: Use To: headers in patch files
It's a minor annoyance when you take the painstaking time to setup To:
headers for each patch in a large series, and then go out to send the
series with git-send-email and watch git ignore the To: headers in the
patch files.

Therefore, always add To: headers from a patch file to the To: headers
for that message. Keep the prompt for the blanket To: header so as to
not break scripts (and user expectations). This means even if a patch
has a To: header, git will prompt for the To: address. Otherwise, we'll
need to introduce interface breakage to either request the header for
each patch missing a To: header or default the header to whatever To:
address is found first (be it in a patch or from user input). Both of
these options don't seem very obvious/useful.

Reported-by: Viresh Kumar <viresh.kumar@st.com>
Signed-off-by: Stephen Boyd <bebarino@gmail.com>
Tested-by: Viresh Kumar <viresh.kumar@st.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
2010-09-29 13:24:04 -07:00
2010-09-27 10:54:17 -07:00
2010-09-03 09:43:45 -07:00
2010-06-13 20:02:50 -07:00
2010-09-15 12:34:48 -07:00
2010-09-04 08:15:36 -07:00
2010-05-31 17:36:27 -07:00
2010-01-29 22:11:00 -08:00
2010-01-29 22:11:00 -08:00
2010-06-21 06:02:49 -07:00
2010-09-08 09:17:01 -07:00
2010-08-18 12:46:55 -07:00
2010-08-18 12:46:55 -07:00
2010-09-08 09:17:01 -07:00
2010-09-03 09:43:45 -07:00
2010-09-03 09:43:45 -07:00
2009-09-13 01:32:26 -07:00
2009-05-20 00:02:24 -07:00
2009-06-18 09:22:46 -07:00
2010-09-09 17:29:40 -07:00
2010-08-21 23:28:31 -07:00
2010-05-07 09:34:27 -07:00
2010-01-20 14:37:25 -08:00
2010-09-08 09:17:01 -07:00
2010-05-28 15:08:27 -07:00
2010-06-21 06:02:49 -07:00
2009-12-13 23:40:24 -08:00
2010-06-13 20:02:50 -07:00
2010-09-26 21:27:37 -07:00
2010-09-18 14:55:08 -07:00
2010-06-30 15:49:18 -07:00
2010-08-22 20:18:37 -07:00
2010-06-21 06:02:44 -07:00
2010-01-21 20:03:45 -08:00
2010-06-21 06:02:44 -07:00
2010-08-12 15:44:51 -07:00
2010-08-09 11:35:46 -07:00
2009-04-22 19:02:12 -07:00
2010-01-12 01:06:09 -08:00
2010-09-12 13:53:03 -07:00
2010-04-01 23:58:30 -07:00
2010-04-01 23:58:30 -07:00
2010-09-06 00:12:04 -07:00
2010-06-22 09:45:22 -07:00
2010-09-03 09:43:41 -07:00
2010-01-20 14:46:35 -08:00
2010-08-21 23:28:31 -07:00
2010-06-21 06:02:45 -07:00
2010-08-31 16:23:31 -07:00
2010-05-04 15:38:58 -07:00
2010-01-21 20:03:45 -08:00
2009-11-04 17:58:15 -08:00
2010-01-20 20:28:50 -08:00
2010-09-27 10:42:11 -07:00
2010-01-17 22:49:36 -08:00
2010-09-06 00:11:59 -07:00
2010-04-12 21:45:17 -07:00
2009-08-23 17:11:28 -07:00
2010-08-14 19:35:37 -07:00
2010-08-14 19:35:37 -07:00
2010-08-14 19:35:38 -07:00
2010-08-14 19:35:37 -07:00
2010-08-26 16:42:59 -07:00
2009-04-20 13:44:14 -07:00
2010-07-25 21:57:23 -07:00
2010-05-24 16:48:32 -07:00
2010-08-16 18:28:27 -07:00
2010-04-02 00:05:31 -07:00
2009-07-22 21:57:41 -07:00

////////////////////////////////////////////////////////////////

	GIT - the stupid content tracker

////////////////////////////////////////////////////////////////

"git" can mean anything, 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

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.
It was originally written by Linus Torvalds with help of a group of
hackers around the net. It is currently maintained by Junio C Hamano.

Please read the file INSTALL for installation instructions.

See Documentation/gittutorial.txt to get started, then see
Documentation/everyday.txt for a useful minimum set of commands, and
Documentation/git-commandname.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).

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

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. 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
http://marc.theaimsgroup.com/?l=git and other archival sites.

The messages titled "A note from the maintainer", "What's in
git.git (stable)" and "What's cooking in git.git (topics)" and
the discussion following them on the mailing list give a good
reference for project status, development direction and
remaining tasks.
Description
Git Source Code Mirror - This is a publish-only repository but pull requests can be turned into patches to the mailing list via GitGitGadget (https://gitgitgadget.github.io/). Please follow Documentation/SubmittingPatches procedure for any of your improvements.
Readme 829 MiB
Languages
C 50.1%
Shell 38.4%
Perl 5.1%
Tcl 3.2%
Python 0.8%
Other 2.1%