[PATCH] fr.po: Fix "uptream" typo

2015-10-21 Thread Thomas Schneider
Signed-off-by: Thomas Schneider --- po/fr.po | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/po/fr.po b/po/fr.po index 581167f..71c4b54 100644 --- a/po/fr.po +++ b/po/fr.po @@ -8862,7 +8862,7 @@ msgstr "" "Si vous souhaitez indiquer l'information de suiv

[PATCH] gitweb: Update logo and favicon

2015-04-12 Thread Thomas Schneider
are necessary for the slightly different aspect ratio of the new one. Graphics were created by Jason Long and are licensed under the CC-BY 3.0 license <https://creativecommons.org/licenses/by/3.0/> Signed-off-by: Thomas Schneider --- View new logos at: https://git.qsuscs.de/cgit/git.gi

Re: [PATCH] checkout: Say “it” instead of “them” for one commit

2015-04-02 Thread Thomas Schneider
Junio – I see you changed my commit message a bit, but some mistakes seem to have slipped in: > checkout: call a single commit “it” instead of “th “them” was cut off, including the trailing quotation mark. […] > them ..."” even for only one commit. Two quotation marks? I always use the “right” qu

Re: git 2.3.4, ssh: Could not resolve hostname

2015-04-02 Thread Thomas Schneider
2015-04-02 22:06 GMT+02:00 Reid Woodbury Jr. : > I'm sure I've seen it other places but I can't remember right now. What you mean is the scp-like syntax: user@host:path/relative/to/home – but if you write user@host:/path/to/something, it’s relative to /. You can also achieve paths relative to the h

[PATCH] checkout: Say “it” instead of “them” for one commit

2015-04-01 Thread Thomas Schneider
When detached and checking out a branch again, git checkout warns about commit(s) that might get lost. It used to say “If you want to keep them […]” even for only one commit. Signed-off-by: Thomas Schneider --- builtin/checkout.c | 11 +-- 1 file changed, 9 insertions(+), 2 deletions

Re: [PATCH] Documentation: Add target to build PDF manpages

2015-03-25 Thread Thomas Schneider
Philip Oakley wrote: > I'd expect 'git help --pdf git' to simply feed the path of git.pdf > (probably in the same directory as the .html versions) to the web > browser and let it determine the users prefered reader. Yes, this is what I would do as well. Unfortunately I don’t really know C, so I c

Re: [PATCH] Documentation: Add target to build PDF manpages

2015-03-20 Thread Thomas Schneider
2015-03-20 22:28 GMT+01:00 Junio C Hamano : > I think you misunderstood me. I am not dismissing the need for PDF; > I am just saying that there is no need to directly generate them > from asciidoc sources, especially when there are already manpages > and html pages available as source to "print" t

Re: [PATCH] Documentation: Add target to build PDF manpages

2015-03-20 Thread Thomas Schneider
2015-03-20 21:21 GMT+01:00 Junio C Hamano : > Stefan Beller writes: > >> ... though how would I read man pages in pdf >> format? I tried searching the web and all I can find is how >> to convert the a man page to pdf. So is there a conveniant >> way to tell `man` to prefer opening pdfs when availa

[PATCH] Documentation: Add target to build PDF manpages

2015-03-20 Thread Thomas Schneider
Signed-off-by: Thomas Schneider --- dblatex does print some warnings, but they seem to be irrelevant. Besides, first patch I submit to git or even to any project using a mailing list … let’s hope I did everything right :) Documentation/Makefile | 9 - 1 file changed, 8 insertions(+), 1