delta/git.git/Documentation/SubmittingPatches, branch ss/userdiff-update-csharp-java

Merge branch 'rs/doc-submitting-patches'

2013-12-12T22:18:29+00:00

* rs/doc-submitting-patches:
  SubmittingPatches: document how to handle multiple patches

SubmittingPatches: document how to handle multiple patches

2013-11-27T19:05:58+00:00

Signed-off-by: Rene Scharfe 
Signed-off-by: Junio C Hamano

Provide some linguistic guidance for the documentation.

2013-08-01T20:13:52+00:00

This will hopefully avoid questions over which spelling and grammar should
be used.  Translators are of course free to create localizations for
specific English dialects.

Signed-off-by: Marc Branchaud 
Signed-off-by: Junio C Hamano

Documentation: the name of the system is 'Git', not 'git'

2013-02-01T21:53:33+00:00

Signed-off-by: Thomas Ackermann 
Signed-off-by: Junio C Hamano

Documentation: avoid poor-man's small caps GIT

2013-02-01T21:53:25+00:00

In the earlier days, we used to spell the name of the system as GIT,
to simulate as if it were typeset with capital G and IT in small
caps.  Later we stopped doing so at around 1.6.5 days.

Let's stop doing so throughout the documentation.  The name to refer
to the whole system (and the concept it embodies) is "Git"; the
command end-users type is "git".  And document this in the coding
guideline.

Signed-off-by: Thomas Ackermann 
Signed-off-by: Junio C Hamano

Merge branch 'jc/submittingpatches'

2013-01-09T16:26:20+00:00

Streamline the document and update with a few e-mail addresses the
patches should be sent to.

* jc/submittingpatches:
  SubmittingPatches: give list and maintainer addresses
  SubmittingPatches: remove overlong checklist
  SubmittingPatches: mention subsystems with dedicated repositories
  SubmittingPatches: who am I and who cares?

SubmittingPatches: give list and maintainer addresses

2013-01-02T17:31:54+00:00

We told readers to "send it to the list" (or the maintainer) without
telling what addresses are to be used.  Correct this.

Signed-off-by: Junio C Hamano

SubmittingPatches: remove overlong checklist

2013-01-02T17:31:09+00:00

The section is no longer a concise checklist.  It also talks about
things that are not covered in the "Long version" text, which means
people need to read both, covering more or less the same thing in
different phrasing.

Fold the details into the main text and remove the section.

Signed-off-by: Junio C Hamano

SubmittingPatches: mention subsystems with dedicated repositories

2013-01-01T22:37:56+00:00

These were only mentioned in periodical "A note from the maintainer"
posting and not in the documentation suite.  SubmittingPatches has a
section to help contributors decide on what commit to base their
changes, which is the most suitable place for this information.

Signed-off-by: Junio C Hamano

SubmittingPatches: who am I and who cares?

2013-01-01T22:35:22+00:00

The introductory text in the "long version" talks about the origin
of this document with "I started ...", but it is unclear who that I
is, and more importantly, it is not interesting how it was started.

Just state the purpose of the document to help readers decide if it
is releavant to them.

Signed-off-by: Junio C Hamano