numbering.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile| 2 +-
Documentation/user-manual.txt | 4 ++--
2 files changed, 3 insertions(+), 3 deletions(-)
diff --git a/Documentation/Makefile b/Documentation/Makefile
index 91a12c7..36c58fc 100644
Ackermann th.ac...@arcor.de
Datum: 04.01.2014 22:18
Betreff: Re: [PATCH] Improve user-manual html and pdf formatting
Hi,
Thomas Ackermann wrote:
--- a/Documentation/user-manual.txt
+++ b/Documentation/user-manual.txt
@@ -1,5 +1,5 @@
-Git User Manual
+#65279;Git User Manual
Why
status
git checkout -b branch
git checkout master
'git status' and 'git checkout master' in repo_b are now
reporting Your branch is up-to-date with 'origin/master'
which is obviously wrong.
---
Thomas
- Original Nachricht
Von: Jiang Xin worldhello@gmail.com
An: Thomas Ackermann
Unfortunately that's not true. In repo_b your ref for origin/master
has not moved. It has remotely (meaning refs/heads/master in repo_a
has moved), but git status is not hitting the remote to find out; it
only looks at the local state. To see what I mean, run git fetch in
repo_b. Once you
But for the simple use case where you only have a master
branch I consider it not really helpful and - at least for me -
misleading.
I see what you mean, and you're not the only one.
Git follows a rule of never contact another machine unless explicitly
asked to using a command such
- Add to Documentation/Makefile
- Start every TODO with a new line
- Fix indentation error
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile| 1 +
Documentation/technical/http-protocol.txt | 3 +--
2 files changed, 2 insertions(+), 2 deletions
Create a proper header when formatted as html.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/technical/pack-heuristics.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/technical/pack-heuristics.txt
b/Documentation/technical/pack
This is a reroll of my attempt to create usable HTML for http-protocol.txt.
The first patch addresses Junio's remarks regarding the conversion to better
ASCIIDOC.
The patch contains some whitespace-only changes so these shouldn't be ignored
while applying.
The second patch tries to fix one of
symbol in HTML
- Use only spaces and not a combination of tabs and spaces for whitespace
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile| 3 +-
Documentation/technical/http-protocol.txt | 232 +++---
2 files changed, 120
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/technical/http-protocol.txt | 45 +++
1 file changed, 22 insertions(+), 23 deletions(-)
diff --git a/Documentation/technical/http-protocol.txt
b/Documentation/technical/http-protocol.txt
index
and not a combination of tabs and spaces for whitespace
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile| 3 +-
Documentation/technical/http-protocol.txt | 232 +++---
2 files changed, 120 insertions(+), 115 deletions(-)
diff --git
please ignore this one
- Original Nachricht
Von: Thomas Ackermann th.ac...@arcor.de
An: git@vger.kernel.org
Datum: 26.01.2014 13:54
Betreff: [PATCH 1/2] create HTML for http-protocol.txt
[PATCH 1/2] create HTML for http-protocol.txt
./Documentation/technical/http
Gerhard Grimm gerhard.grimm at detec.com writes:
In order to set up automated builds and tests of the CMake toolchain
(www.cmake.org) on HP-UX 11.11 (hppa)
and 11.23 (ia64), I needed to install git on those platforms.
The latest binary package available from hpux.connect.org.uk is version
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/git-http-backend.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/git-http-backend.txt
b/Documentation/git-http-backend.txt
index e8c13f6..d422ba4 100644
--- a/Documentation/git-http
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/RelNotes/2.2.0.txt| 6 +++---
Documentation/config.txt| 10 +-
Documentation/git-bisect-lk2009.txt | 4 ++--
Documentation/git-clean.txt
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/gittutorial.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/gittutorial.txt b/Documentation/gittutorial.txt
index af9f709..710e636 100644
--- a/Documentation/gittutorial.txt
+++ b
I also re-read the whole document and think it's still up-to-date
with Git 2.0. But I might have missed some subtler points.
Thomas
- Original Nachricht
Von: Junio C Hamano gits...@pobox.com
An: Thomas Ackermann th.ac...@arcor.de
Datum: 11.11.2014 23:51
Betreff: Re: [PATCH
historical note from Object storage format
[PATCH 11/13] Remove obscure reference from Examples
[PATCH 12/13] Remove irrelevant reference from Tying it all together
[PATCH 13/13] git prune is safe now
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Thomas
--
To unsubscribe from this list: send
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index fe723e4..103ec9a 100644
--- a/Documentation/user-manual.txt
+++ b
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 17 -
1 file changed, 12 insertions(+), 5 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 103ec9a..cb30929 100644
--- a/Documentation/user
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 13 +
1 file changed, 5 insertions(+), 8 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index cb30929..b450980 100644
--- a/Documentation/user-manual.txt
git pull . works, but git merge is the recommended
way for new users to do things. (The old description
also should have read The former is actually *not* very
commonly used.)
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 15 ++-
1 file
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index ca78333..ccbddc7 100644
--- a/Documentation/user-manual.txt
+++ b
Combine the two cases for git add into one.
Add verb use to git rm case.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 11 +++
1 file changed, 3 insertions(+), 8 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user
Describe the conflict resolution in terms of the
commands the user is supposed to use.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 6 ++
1 file changed, 2 insertions(+), 4 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user
Add some missing punctuation.
Simplify description of git branch -d/-D.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 19 +++
1 file changed, 7 insertions(+), 12 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user
Remove unnecessary quoting.
Simplify description of three-way merge.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user
Sorry Jon, but this might not be of any help to new Git users ;)
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 0d3f04e
I wonder if this longer wall of text (added in 13be3e31, 2010-01-29)
is too aggressive.
It is the only piece of advice that I explicitly disable in
~/.gitconfig, so I haven't looked at it again for a while. Since
then, the usual stream of questions about how to recover from people
who
Sure. I wonder if there should be some text to replace the output
that mentions the pack being created, though. E.g.:
You can then run
Total 6020 (delta 4070), reused 0 (delta 0)
-Or you can use linkgit:git-name-rev[1], which will give the commit a
+or you can use linkgit:git-name-rev[1], which will give the commit a
I think this reads better with a capital 'O'. (The pedant in me
likes it, too, since a colon ends a sentence.)
The lowercase 'but' later in
That's a mouthful. I'd say
To update the index with the contents of a new or modified file, use
OK; thanks! I will change this.
---
Thomas
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info
- A test tree into which patches are initially placed so that they
can get some exposure when integrated with other ongoing development.
- This tree is available to Andrew for pulling into -mm whenever he
- wants.
This drops useful information (namely, that Tony was
Hm. It's been too long since I was a novice, since I find the above
clear already.
OK; I will drop that patch.
---
Thomas
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at
But is this correct? I somehow thought that we check with the
current or the upstream.
You are correct. I will add this. Thanks.
---
Thomas
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info at
Maybe the intent is
Git can help you perform a three-way merge, which can in turn be
used for a many-way merge by repeating the merge procedure several
times. The usual situation is that you only do one three-way merge
(reconciling two lines of history) and commit
- this patch was dropped
[PATCH 12/13] Remove irrelevant reference from Tying it all together
- same as in v1
[PATCH 13/13] git prune is safe now
- weakend warning for git prune
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Thomas
--
To unsubscribe from this list: send the line unsubscribe
Reviewed-by: Jonathan Nieder jrnie...@gmail.com
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index fe723e4..103ec9a 100644
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 19 +--
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 103ec9a..bdefd9a 100644
--- a/Documentation/user
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 16 +++-
1 file changed, 7 insertions(+), 9 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index bdefd9a..3f44ca0 100644
--- a/Documentation/user-manual.txt
git pull . works, but git merge is the recommended
way for new users to do things. (The old description
also should have read The former is actually *not* very
commonly used.)
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 8
1 file changed, 4
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
index 6241a43..465d9cb 100644
--- a/Documentation/user
Add some missing punctuation.
Simplify description of git branch -d/-D.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 20
1 file changed, 8 insertions(+), 12 deletions(-)
diff --git a/Documentation/user-manual.txt b/Documentation
Sorry Jon, but this might not be of any help to new Git users ;)
Acked-by: Jon Loeliger j...@jdl.com
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 3 +--
1 file changed, 1 insertion(+), 2 deletions(-)
diff --git a/Documentation/user-manual.txt b
git prune is safe in case of concurrent accesses to a repository
but using it in such a case is not recommended.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 12 +++-
1 file changed, 3 insertions(+), 9 deletions(-)
diff --git a/Documentation
Remove unnecessary quoting.
Simplify description of three-way merge.
Signed-off-by: Jonathan Nieder jrnie...@gmail.com
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/user-manual.txt | 27 +--
1 file changed, 13 insertions(+), 14 deletions(-)
diff
Hi,
I am using MsysGit 1.7.11 on WinXP 32 bit and experience the folllowing strange
behaviour:
For a file like File.txt in the repo, git blame file.txt (note the lower
case)
shows Not commited yet for every single line in the file.
git blame File.txt (correct upper case spelling) gives the
You are right but as I mentioned in my posting I am using core.ignorecase=true
so I expected file.txt and File.txt to be treated the same.
The man-page for git-config says:
core.ignorecase
If true, this option enables various workarounds to enable git to work better
on filesystems that are not
Hi,
I wanted to have a single PDF file which contains the complete Git
documentation
(except user-manual) for easier reading on my tablet. The simplest way to do
this was by using wkhtmltopdf which can combine a set of HTML files into a
sinlge
PDF file and also apply some reformatting. To
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/git-bisect-lk2009.txt | 12 ++--
Documentation/git-fetch-pack.txt| 5 -
2 files changed, 10 insertions(+), 7 deletions(-)
diff --git a/Documentation/git-bisect-lk2009.txt
b/Documentation/git-bisect-lk2009.txt
- add missing files
- fix some asciidoc layout problems
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile| 12 ++-
Documentation/technical/index-format.txt | 2 +-
Documentation/technical/pack-format.txt | 8 +++
Documentation
- create html for all release note files
- fix some asciidoc layout problems
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile | 2 ++
Documentation/RelNotes/1.5.2.1.txt | 6 --
Documentation/RelNotes/1.6.0.2.txt | 6 --
Documentation/RelNotes
- add missing files
- fix some asciidoc layout problems
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile | 10 +
Documentation/howto/maintain-git.txt | 4 ++
.../howto/rebase-from-internal-branch.txt | 11
- use wkhtmltopdf to combine all html files into a single pdf file git-doc.pdf
- provide make target fullpdf to create git-doc.pdf
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/.gitignore | 1 +
Documentation/Makefile| 9 +
Documentation/footerend.txt
.
- Original Nachricht
Von: Jeff King p...@peff.net
An: Junio C Hamano gits...@pobox.com
Datum: 06.10.2012 21:10
Betreff: Re: [Patch 1/5] Fix some asciidoc layout problems
On Sat, Oct 06, 2012 at 11:39:13AM -0700, Junio C Hamano wrote:
Thomas Ackermann th.acke...@arcor.de writes
to create git-doc.pdf.
If you want to have a quick look on the resulting pdf just clone
https://github.com/tacker66/git-docpdf.git. This repo contains
a current version of user.manual.pdf and git-doc.pdf
- Original Nachricht
Von: Jeff King p...@peff.net
An: Thomas Ackermann
Hi,
here is my reworked patch series for creating a single PDF for all
git documentation files.
Thanks to Junio Hamano, Philip Oakley and Jeff King for your comments!
In general, the following problems had to be fixed in doc files in order to
create
HTML by using asciidoc and afterwards
From 27b3105a374158fb8cb008c808a1ef94487a48f7 Mon Sep 17 00:00:00 2001
From: Thomas Ackermann th.ac...@arcor.de
Date: Thu, 4 Oct 2012 19:11:43 +0200
Subject: [PATCH] Split over-long synopsis in git-fetch-pack.txt into several
lines
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
From e7c97695b676e1ebe66491b3ed256051b9a3b4f1 Mon Sep 17 00:00:00 2001
From: Thomas Ackermann th.ac...@arcor.de
Date: Thu, 4 Oct 2012 19:11:43 +0200
Subject: [PATCH] Shorten two over-long lines in git-bisect-lk2009.txt by
removing some white-space
Signed-off-by: Thomas Ackermann th.ac
From af1f0dc8e02ef178fc89f5fa3893a997a4a9b2eb Mon Sep 17 00:00:00 2001
From: Thomas Ackermann th.ac...@arcor.de
Date: Tue, 9 Oct 2012 20:19:34 +0200
Subject: [PATCH] Change headline of technical/send-pack-pipeline.txt to not
confuse its content with content from git-send-pack.txt
Signed-off
From 23b5272cbb27dca7e292f33c79cf3d8e21298b78 Mon Sep 17 00:00:00 2001
From: Thomas Ackermann th.ac...@arcor.de
Date: Sat, 29 Sep 2012 10:00:00 +0200
Subject: [PATCH] Prerequisites for creating nice html for all files in
Documentation/technical
- fix wrong asciidoc sectioning markup in index
From cd7a26f5e7ba8cc42bf81e1b78f800460510b71f Mon Sep 17 00:00:00 2001
From: Thomas Ackermann th.ac...@arcor.de
Date: Sat, 29 Sep 2012 11:00:00 +0200
Subject: [PATCH] Prerequisites for creating nice html for all files in
Documentation/RelNotes
- remove left-over shell-script fragments from some
From 31f86526e0a0bd00be57db3275c860913f668fb8 Mon Sep 17 00:00:00 2001
From: Thomas Ackermann th.ac...@arcor.de
Date: Mon, 1 Oct 2012 20:06:48 +0200
Subject: [PATCH] Create pdf from all html files
- use wkhtmltopdf (patched QT version) to combine all html files into a
single pdf file git-doc.pdf
From ac7de86bd58c5849c12e2b05e7b7f68704d9093e Mon Sep 17 00:00:00 2001
From: Thomas Ackermann th.ac...@arcor.de
Date: Wed, 10 Oct 2012 19:30:55 +0200
Subject: [PATCH] Wire everything into Makefile and Documentation/Makefile
- target html creates html for all files in Documentation/howto
Hi,
this is v3 of my patch series for creating a single PDF for all
git documentation files.
There are only 2 changes since v2 (thanks to Junio for pointing me at these
issues) :
- The over-long lines in git-bisect-lk2009.txt where shortened by abbreviating
the SHA1s.
- Pretty-printing the
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/git-fetch-pack.txt | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/Documentation/git-fetch-pack.txt b/Documentation/git-fetch-pack.txt
index 474fa30..12cd8a2 100644
--- a/Documentation/git-fetch-pack.txt
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/git-bisect-lk2009.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/git-bisect-lk2009.txt
b/Documentation/git-bisect-lk2009.txt
index 8a2ba37..ec4497e 100644
--- a/Documentation/git
- target html creates html for all files in Documentation/howto and
Documentation/technical
- new target relnoteshtml creates html for all release notes
- new target fullpdf creates git-doc.pdf and uses targets html,
relnoteshtml and pdf
- html does not use relnoteshtml
Signed-off-by: Thomas
- Original Nachricht
Von: Junio C Hamano gits...@pobox.com
An: Thomas Ackermann th.acke...@arcor.de
Datum: 17.10.2012 00:11
Betreff: Re: [Patch v3 0/8] Create single PDF for all HTML files
I (and other people who wrote documentation, I suspect, as well)
feel somewhat
That means that for the patch [6/8], which adds content-type to the
text files, to be complete, it needs to update Makefile to produce
html files from them.
IMHO also for the new files in ./technical html should be created because
now as we have asciidoc markup why not also use it.
This patch adds rules to the html taget in Documentation/Makefile to create
html
also for the new asciidoc files in Documentation/technical and
Documentation/howto
which were added in this topic.
---
Thomas
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a
- target html creates html for all files in Documentation/howto and
Documentation/technical
Signed-off-by: Thomas Ackermann th.acke...@arcor.de
---
Documentation/Makefile | 26 --
1 file changed, 24 insertions(+), 2 deletions(-)
diff --git a/Documentation/Makefile b
This target was only used to create user-manual.pdf with dblatex
using a separate style definition than was used for user-manual.html.
These two style definitions had to be maintained separately and
so made improvements to user-manual.html unnecessarily hard.
Signed-off-by: Thomas Ackermann
I don't understand. Do you mean that you want to change the rules
that generate user-manual.xml? Would generating different XML files
for the PDF and for other purposes (with different names) work as a
way to achieve that without losing the printable manual?
This would be even worse
If I understood the original commit message correctly, you were saying
the XML file was not suitable for html generation and you wanted to
tweak it, and were dropping the PDF target to avoid breaking it. Now
if I understand correctly you are saying the XML file actually *is*
suitable for
- Start list with 1 instead of 0 because ASCIIDOC will renumber it anyway
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/technical/api-command.txt | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/Documentation/technical/api-command.txt
b
- because it describes a different form of API than the other api-* documents
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/technical/api-index.sh | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/Documentation/technical/api-index.sh
b/Documentation
OK; I would also prefer to have it in ./howto.
So please drop this patch; I will provide a new one.
- Original Nachricht
Von: Junio C Hamano gits...@pobox.com
An: Thomas Ackermann th.ac...@arcor.de
Datum: 16.12.2012 21:01
Betreff: Re: [PATCH] Move api-command.txt to the end
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile | 1 -
1 file changed, 1 deletion(-)
diff --git a/Documentation/Makefile b/Documentation/Makefile
index 3615504..7df75d0 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -31,7 +31,6 @@ SP_ARTICLES
to ./Documentation/Makefile
[PATCH 3/3] Amend new-command.txt to be processed correctly by howto-index.sh
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Thomas
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to majord...@vger.kernel.org
More majordomo info
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/{technical/api-command.txt = howto/new-command.txt} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename Documentation/{technical/api-command.txt = howto/new-command.txt}
(100%)
diff --git a/Documentation/technical/api
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/Makefile b/Documentation/Makefile
index 7df75d0..f3afcb6 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -21,6 +21,7 @@ ARTICLES
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/howto/new-command.txt | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git a/Documentation/howto/new-command.txt
b/Documentation/howto/new-command.txt
index d3b9781..36502f6 100644
--- a/Documentation
Howto documents in howto-index.txt were listed in a rather
random order. So better sort them.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/Documentation/Makefile b/Documentation/Makefile
index
I think $(wildcard) used to sort but in recent GNU make it no longer
does, so this is probably a good change.
Do we need to explicitly sort the api-index as well? $(API_DOCS) is
fed to the script that reads filenames one at a time in the given
order, but I do not see anybody asking for
This file is rather outdated and IMHO shouldn't be there in the first place.
(If there are translations of the Git documentation they are better be kept
separate from the original documentation.)
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/pt_BR/gittutorial.txt | 675
CodingGuidelines and SubmittingPatches are IMHO a little bit hidden in
./Documentation
and with respect to their content should be better placed in
./Documentation/technical.
[PATCH 1/3] Move CodingGuidelines to ./technical/coding-guidelines.txt and
SubmittingPatches to
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/{CodingGuidelines = technical/coding-guidelines.txt} | 0
Documentation/{SubmittingPatches = technical/submitting-patches.txt} | 0
2 files changed, 0 insertions(+), 0 deletions(-)
rename Documentation/{CodingGuidelines
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/Makefile | 2 ++
1 file changed, 2 insertions(+)
diff --git a/Documentation/Makefile b/Documentation/Makefile
index e53d333..a51c00f 100644
--- a/Documentation/Makefile
+++ b/Documentation/Makefile
@@ -47,6 +47,8 @@ TECH_DOCS
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/technical/coding-guidelines.txt | 175 ++---
Documentation/technical/submitting-patches.txt | 144 ++--
2 files changed, 174 insertions(+), 145 deletions(-)
diff --git a/Documentation
to ./technical (sorry for
being the guy who just moved ./technical/api-command to
./howto/new-command.txt ;-)).
./Documentation itself should only contain the command manpages
and tutorials.
- Original Nachricht
Von: Ramkumar Ramachandra artag...@gmail.com
An: Thomas Ackermann th.ac
Implementation details are part of API; CG and SP are social not
technical.
This depends on your definition of social ;-)
Also CG and SP are in the part of the documents that are not
installed for end-users and that is their right place. They matter
only to the people who grab our
Junio C Hamano gitster at pobox.com writes:
Thanks; I just realized that nothing in Documentation/ hierarchy
mentions these; they are only mentioned in A Note from the
Maintainer I send out every once in a while (kept in MaintNotes of
'todo' branch):
Wouldn't it be a good idea to put
Git changed its 'official' system name from 'GIT' to 'Git' in v1.6.5.3
(as can be seen in the corresponding release note where 'GIT' was
changed to 'Git' in the header line).
Alas the documention uses 'GIT', 'Git' or even 'git' to refer to the
Git system. So change every occurrence of 'GIT and
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
---
Documentation/asciidoc.conf | 2 +-
Documentation/everyday.txt | 4 ++--
Documentation/git-clone.txt | 2 +-
Documentation/git-cvsexportcommit.txt | 2
What about GITweb?
You are right; I missed that because I grepped only for 'GIT' as a whole word.
'gitweb' and 'GITweb' should be changed to 'Gitweb'.
IMO some of these look nicer when everything is lowercase.
e.g. standard git committer ident format.
IMHO what seems nicer here is
Git changed its 'official' system name from 'GIT' to 'Git' in v1.6.5.3
(as can be seen in the corresponding release note where 'GIT' was
changed to 'Git' in the header line).
Alas the documention uses 'GIT', 'Git' or even 'git' to refer to the
Git system. So change every occurrence of
If I were to decide today to change the spellings, with an explicit
purpose of making things more consistent across documentation, it
may make sense to use even a simpler rule that is less error-prone
for people who write new sentences that has to have the word. How
about treating it just
Git changed its 'official' system name from 'GIT' to 'Git' in v1.6.5.3
(as can be seen in the corresponding release note where 'GIT' was
changed to 'Git' in the header line).
Alas the documention uses 'GIT', 'Git' or even 'git' to refer to the
Git system. So change every occurrence of 'GIT and
Git changed its 'official' system name from 'GIT' to 'Git' in v1.6.5.3
(as can be seen in the corresponding release note where 'GIT' was
changed to 'Git' in the header line). So change every occurrence
of 'GIT in the documention to 'Git'.
Signed-off-by: Thomas Ackermann th.ac...@arcor.de
1 - 100 of 141 matches
Mail list logo
