Check repository configuration gitweb.description for project description,

if $GIT_DIR/description does not exist
Signed-off-by: Bruno Ribas <ribas@c3sl.ufpr.br>

---

 contrib/hooks/post-receive-email |    6 +++++-

 1 files changed, 5 insertions(+), 1 deletions(-)
diff --git a/contrib/hooks/post-receive-email b/contrib/hooks/post-receive-email

index 77c88eb..bdd21fa 100644

--- a/contrib/hooks/post-receive-email

+++ b/contrib/hooks/post-receive-email

@@ -614,7 +614,11 @@ if [ -z "$GIT_DIR" ]; then

 	exit 1

 fi
-projectdesc=$(sed -ne '1p' "$GIT_DIR/description")

+if [ -f "$GIT_DIR/description" ]; then

+	projectdesc=$(sed -ne '1p' "$GIT_DIR/description")

+else

+	projectdesc=$(git-config gitweb.description)

+fi

 # Check if the description is unchanged from it's default, and shorten it to

 # a more manageable length if it is

 if expr "$projectdesc" : "Unnamed repository.*$" >/dev/null

--

1.5.4.24.gce08d
-

(but this can be fixed when applying).
--

Jakub Narebski

Poland

ShadeHawk on #git

-

I can resend with no problem =)
--

Bruno Ribas - ribas@c3sl.ufpr.br

http://web.inf.ufpr.br/ribas

C3SL: http://www.c3sl.ufpr.br

-

Forgoten?! 8^)
--

Bruno Ribas - ribas@c3sl.ufpr.br

http://web.inf.ufpr.br/ribas

C3SL: http://www.c3sl.ufpr.br

-

More like "not so much interested myself, although I did not

have strong objection either".
Typically original author or people who would see much value in

the patch than myself have more incentive and motivation to keep

pushing for inclusion of such a patch, so I tend to trust them

to re-send saying "Here is the final for inclusion, the list

concensus was favorable, and I addressed all the issues raised

during the discussion." if they still care about the patch than

actively fishing for old patches from my mailbox.
On the other hand if such re-push never happens that is a good

indication that nobody is convinced strongly enough to stand

behind the patch, and my time is better spent elsewhere.

-