Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-07-02 Thread Junio C Hamano
Michael Haggerty writes: > I have a logistical question: git-multimail doesn't have its own mailing > list, and GitHub doesn't offer one. I was thinking about setting up a > Google group, but a few people at GitMerge suggested that I instead > direct discussion of git-multimail to the main Git m

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-07-02 Thread Michael Haggerty
On 07/01/2013 11:58 PM, Junio C Hamano wrote: > Michael Haggerty writes: > >> My understanding is that we are waiting on two things: >> >> 1. Consensus from the community. I would characterize the feedback on >> the mailing list as limited in quantity but strongly positive [1-4] and >> I think t

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-07-01 Thread Junio C Hamano
Michael Haggerty writes: > My understanding is that we are waiting on two things: > > 1. Consensus from the community. I would characterize the feedback on > the mailing list as limited in quantity but strongly positive [1-4] and > I think that most/all of the wishes for post-receive-email featu

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-07 Thread Matthieu Moy
Junio C Hamano writes: > I have a mildly strong suspicion that a better approach might be to: > > - Copy the current stable snapshot to the contrib/ area, [...] > > - Keep the development at your GitHub repository, [...] > > - Update what is in contrib/ in my tree with a stable snapshot, >

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-07 Thread Junio C Hamano
Michael Haggerty writes: > My understanding is that we are waiting on two things: > > 1. Consensus from the community. I would characterize the feedback on > the mailing list as limited in quantity but strongly positive [1-4] and > I think that most/all of the wishes for post-receive-email featu

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-07 Thread Junio C Hamano
Matthieu Moy writes: > OTOH, it's not urgent, people can already use git-multimail by taking it > from GitHub. Yes. There are less and less reason to rush things into contrib/ these days, which is a very good thing from ecosystem's point of view. It is a sign that Git has matured that my tree

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-07 Thread Matthieu Moy
Junio C Hamano writes: > Matthieu Moy writes: > >> More precisely: you should have a look at git-multimail (in directory >> contrib/, in branch for now pu/, or from >> https://github.com/mhagger/git-multimail) before spending time on >> post-receive-email. > > Oh, by the way, is this a vote of c

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-07 Thread Michael Haggerty
On 05/07/2013 08:36 AM, Junio C Hamano wrote: > Matthieu Moy writes: > >> More precisely: you should have a look at git-multimail (in directory >> contrib/, in branch for now pu/, or from >> https://github.com/mhagger/git-multimail) before spending time on >> post-receive-email. > > Oh, by the w

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-06 Thread Junio C Hamano
Matthieu Moy writes: > More precisely: you should have a look at git-multimail (in directory > contrib/, in branch for now pu/, or from > https://github.com/mhagger/git-multimail) before spending time on > post-receive-email. Oh, by the way, is this a vote of confidence in that topic, hinting th

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-06 Thread Trond Hasle Amundsen
Matthieu Moy writes: >>> The included patch attempts to improve post-receive-email. It's a >> >> Please don't ;-) > > More precisely: you should have a look at git-multimail (in directory > contrib/, in branch for now pu/, or from > https://github.com/mhagger/git-multimail) before spending time o

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-06 Thread Trond Hasle Amundsen
2001 >> From: Trond Hasle Amundsen >> Date: Mon, 6 May 2013 15:41:25 +0200 >> Subject: [PATCH] contrib/hooks/post-receive-email: get description from >> repo.git/config > > And remove these five lines above. We will read the authorship and > subject from the e-m

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-06 Thread Matthieu Moy
Junio C Hamano writes: > Trond Hasle Amundsen writes: > >> Hello, >> >> The included patch attempts to improve post-receive-email. It's a > > Please don't ;-) More precisely: you should have a look at git-multimail (in directory contrib/, in branch for now pu/, or from https://github.com/mhagge

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-06 Thread Junio C Hamano
9b9023f1f188c844b Mon Sep 17 00:00:00 2001 > From: Trond Hasle Amundsen > Date: Mon, 6 May 2013 15:41:25 +0200 > Subject: [PATCH] contrib/hooks/post-receive-email: get description from > repo.git/config And remove these five lines above. We will read the authorship and subject from the

Re: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-06 Thread Trond Hasle Amundsen
not on the list. Bah.. It seems I attached this as MIME, sorry about that. Here it is, properly inlined this time: >From 878a7af9088e2bcc3afc9b09b9023f1f188c844b Mon Sep 17 00:00:00 2001 From: Trond Hasle Amundsen Date: Mon, 6 May 2013 15:41:25 +0200 Subject: [PATCH] contrib/hooks/post-recei

[PATCH] contrib/hooks/post-receive-email: get description from repo.git/config

2013-05-06 Thread Trond Hasle Amundsen
st. >From 878a7af9088e2bcc3afc9b09b9023f1f188c844b Mon Sep 17 00:00:00 2001 From: Trond Hasle Amundsen Date: Mon, 6 May 2013 15:41:25 +0200 Subject: [PATCH] contrib/hooks/post-receive-email: get description from repo.git/config When getting the project description, we first try gitweb.description entry in repo.git/config,