delta/git.git/Documentation/git-remote.txt, branch sb/string-list-split-appends

Merge branch 'xf/user-manual-markup'

2015-10-29T20:59:14+00:00

AsciiDoc markup fixes.

* xf/user-manual-markup:
  Documentation: match undefline with the text in old release notes
  Documentation: match underline with the text
  Documentation: fix header markup

Documentation: match underline with the text

2015-10-22T17:16:12+00:00

Even though AsciiDoc is more lenient when deciding if an underline
is for the contents on the previous line to find section headers, we
should match the length of them for other formatters to help them.

Signed-off-by: Junio C Hamano

remote: add get-url subcommand

2015-09-17T19:19:57+00:00

Expanding `insteadOf` is a part of ls-remote --url and there is no way
to expand `pushInsteadOf` as well. Add a get-url subcommand to be able
to query both as well as a way to get all configured urls.

Signed-off-by: Ben Boeckel 
Signed-off-by: Junio C Hamano

Merge branch 'mg/doc-remote-tags-or-not'

2015-03-06T23:02:28+00:00

"git remote add" mentioned "--tags" and "--no-tags" and was not
clear that fetch from the remote in the future will use the default
behaviour when neither is given to override it.

* mg/doc-remote-tags-or-not:
  git-remote.txt: describe behavior without --tags and --no-tags

git-remote.txt: describe behavior without --tags and --no-tags

2015-03-02T20:48:23+00:00

Signed-off-by: Michael J Gruber 
Signed-off-by: Junio C Hamano

Documentation/git-remote.txt: stress that set-url is not for triangular

2015-01-29T22:07:13+00:00

It seems to be a common mistake to try using a single remote
(e.g. 'origin') to fetch from one place (i.e. upstream) while
pushing to another (i.e. your publishing point).

That will never work satisfactorily, and it is easy to understand
why if you think about what refs/remotes/origin/* would mean in such
a world.  It fundamentally cannot reflect the reality.  If it
follows the state of your upstream, it cannot match what you have
published, and vice versa.

It may be that misinformation is spread by some people.  Let's
counter them by adding a few words to our documentation.

 - The description was referring to  and , but never
   mentioned  argument you give from the command line.  By
   mentioning "remote ", stress the fact that it is configuring
   a single remote.

 - Add a reminder that explicitly states that this is about a single
   remote, which the triangular workflow is not about.

Signed-off-by: Junio C Hamano

docs/git-remote: capitalize first word of initial blurb

2014-02-11T19:03:07+00:00

All other man files have capitalized descriptions which
immediately follow the command's name. Let's capitalize
this one too for consistency.

Signed-off-by: Albert L. Lash, IV 
Signed-off-by: Junio C Hamano

remote doc: document long forms of set-head options

2013-09-27T23:49:18+00:00

"git remote set-head" has always supported --add and --delete
as synonyms for the -a and -d option but forgot to document
them.

Signed-off-by: Philip Oakley 
Signed-off-by: Jonathan Nieder

Documentation: Update the NFS remote examples to use the staging repo

2013-06-23T06:35:17+00:00

linux-nfs.org seems to have restructured their repository layout since
8391c60 (git-remote.txt: fix example url, 2007-11-02), and Bruce's
repo is now at git://git.linux-nfs.org/projects/bfields/linux.git.
Bruce also has a more richer internal branch structure (master,
everything, for-3.1, ...), so updating the existing example to use his
current repo may be confusing.

To simplify, I've replaced the NFS repo with Greg's staging repo.
I've also updated the output of the surrounding commands to match the
output of a current run through.

Signed-off-by: W. Trevor King 
Signed-off-by: Junio C Hamano

documentation: trivial style cleanups

2013-05-17T19:09:21+00:00

White-spaces, missing braces, standardize --[no-]foo.

Signed-off-by: Felipe Contreras 
Signed-off-by: Junio C Hamano