trace.c: do not mark getnanotime() as "inline"

Oracle Studio compilers don't allow for static variables in
functions that are defined to be inline. GNU C does permit this.

Let's reference the C99 standard though, which doesn't allow for
inline functions to contain modifiable static variables.

Signed-off-by: Ben Walton <bdwalton@gmail.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
completion: use "git -C $there" instead of (cd $there && git ...)

We have had "git -C $there" to first go to a different directory
and run a Git command without changing the arguments for quite some
time.  Use it instead of (cd $there && git ...) in the completion
script.

This allows us to lose the work-around for misfeatures of modern
interactive-minded shells that make "cd" unusable in scripts (e.g.
end users' $CDPATH taking us to unexpected places in any POSIX
shell, and chpwd functions spewing unwanted output in zsh).

Based on Øystein Walle's idea, which was raised during the
discussion on the solution by Brandon Turner for a problem zsh users
had with RVM which mucks with chpwd_functions in users' environments
(https://github.com/wayneeseguin/rvm/issues/3076).

As $root variable, which is used to direct where to chdir to, is set
to "." based on if $2 to __git_index_files is set (not if it is empty),
the only caller of the function is fixed not to pass the optional $2
when it does not want us to switch to a different directory.  Otherwise
we would end up doing "git -C '' command...", which would not work.

Maybe we would want "git -C '' command..." to mean "do not chdir
anywhere", but that is a spearate topic.

Signed-off-by: Junio C Hamano <gitster@pobox.com>
doc: modernise everyday.txt wording and format in man page style

Refresh the contents of everyday.txt contents to a more modern
command style. Also update the mark-up so that it can be formatted
as a man page with AsciiDoc ready for transfer to the Git guides.
The transfer is in subsequent commits.

Guidance on modernising the command style provided by Junio at [1],
[2] and [3].

[1] Individual Developer, both Standalone and Participant
http://article.gmane.org/gmane.comp.version-control.git/254269
[2] Integrator
http://article.gmane.org/gmane.comp.version-control.git/254502
[3] Administrator
http://article.gmane.org/gmane.comp.version-control.git/254824

Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Philip Oakley <philipoakley@iee.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
doc: Makefile regularise OBSOLETE_HTML list building

Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Philip Oakley <philipoakley@iee.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
doc: add 'everyday' to 'git help'

The "Everyday GIT With 20 Commands Or So" is not accessible via the
Git help system.  Move everyday.txt to giteveryday.txt so that "git
help everyday" works, and create a new placeholder file everyday.html
to refer people who follow existing URLs to the updated location.

giteveryday.txt now formats well with AsciiDoc as a man page and
refreshed content to a more command modern style.

Add 'everyday' to the help --guides list and update git(1) and 5
other links to giteveryday.

Signed-off-by: Philip Oakley <philipoakley@iee.org>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
Merge branch 'po/everyday-doc'

"git help everyday" to show the Everyday Git document.

* po/everyday-doc:
  doc: add 'everyday' to 'git help'
  doc: Makefile regularise OBSOLETE_HTML list building
  doc: modernise everyday.txt wording and format in man page style
Merge branch 'bw/trace-no-inline-getnanotime'

No file-scope static variables in an inlined function, please.

* bw/trace-no-inline-getnanotime:
  trace.c: do not mark getnanotime() as "inline"
Merge branch 'jc/completion-no-chdir'

* jc/completion-no-chdir:
  completion: use "git -C $there" instead of (cd $there && git ...)
l10n: git.pot: proposed updates for v2.2.0 (+49)

The 1st round of Git l10n often starts very late duing the release
cycle of Git, usually after the release of rc0. This leads to a
gaint update of "po/git.pot" and lots of works for translators with
a tight deadline (about one week).

This "pu" branch holds proposed updates of the file "po/git.pot" for
Git next release (2.2.0), and will be updated and rewound without
notification when there are remarkable updates for it.

Translators could work on this "pu" branch before the l10n coordinator
starts the 1st round of l10n for this release cycle of Git, then
cherry-pick or rebase their work(s) onto the master branch, and send
pull request to the l10n coordinator later.

Please note:

 1. Because this branch will be rewound occasionally, translators
    SHOULD NOT merge, but SHOULD rebase their work(s) to the rewound
    "pu" branch instead.

        $ git fetch git://github.com/git-l10n/git-po.git pu
        $ git rebase --onto FETCH_HEAD HEAD~1

 2. Update your translated message file "po/XX.po".

        $ msgmerge --add-location --backup=off -U "po/XX.po" \
          po/git.pot

 3. Then start to translate "po/XX.po" and commit.

 4. DO NOT send pull request to the l10n coordinator for
    translations on this "pu" branch.

 5. When the l10n coordinator starts the 1st round l10n for the
    current Git release cycle, translators should rebase their works
    onto the master branch, review the translations and then send pull
    request.

        $ git fetch git://github.com/git-l10n/git-po.git master
        $ git rebase --onto FETCH_HEAD HEAD~1

Signed-off-by: Jiang Xin <worldhello.net@gmail.com>