- add example

[TLD.git] / git-howto.txt

diff --git a/git-howto.txt b/git-howto.txt
index ca23bbf63e7217fcb484b28c5d7d0bb485aaf4e1..3a24fb2511eb1096b80f6eb503279ae5ad96abd1 100644 (file)
--- a/git-howto.txt
+++ b/git-howto.txt
@@ -18,6 +18,7 @@ Table Of Content:
 4. I've deleted some files in my cloned repo. I'm doing git pull, but they
    do not reappear.
 5. How can I add a description to a new repository?
+6. SPECS: What is obsolete now that we have GIT?
 
 ==============================================================================
 1. How do I commit a new .spec file or package to the repository?
@@ -113,5 +114,30 @@ git ls-files -d | xargs git checkout --
 
 Do the following:
 
-ssh git@git.tld-linux.org setdesc packages/some_package "Some description"
+echo "Some description" |ssh git@git.tld-linux.org setdesc packages/some_package
 
+Ex.
+
+$ echo "kernel-desktop, a linux version optimised for the desktop" |ssh git@git.tld-linux.org setdesc packages/kernel-desktop
+New description is:
+kernel-desktop, a linux version optimised for the desktop
+$
+
+==============================================================================
+6. SPECS: What is obsolete now that we have GIT?
+
+Now that we use GIT for our own .spec files and projects, there're some things
+we do no longer need.
+
+a) Remove "# $Revision:" lines on top of a .spec file
+b) Remove the whole changelog from the bottom of a .spec file
+c) Remove "%define date    %(echo `LC_ALL="C" date +"%a %b %d %Y"`)"
+d) Remove feedback stuff and all PLD related links
+
+Why all that removing?
+There're a couple of reasons why we don't want to keep these things in our 
+specs.
+Most of them are strictly CVS related, like the Revision stuff. We don't need
+to artificially increase the size of our .spec files by having the whole 
+changelog included in them. Use "git log", with all its sophisticated options,
+to visualise changes, make statistics etc.