Fwd: [koha-commits] main Koha release repository branch, master, updated. v3.02.00-188-g4b69538
I think this was brought up before but how do I know what has changed in these files? Commit emails that tell me bug numbers and a short title/summary are much more helpful than this. I use these emails to determine what to update in the manual and I can't keep track if I have to go hunt down these commit numbers. Is there another way to format these types of messages to look like the ones that include details about each patch? Nicole ---------- Forwarded message ---------- From: Git repo owner <gitmaster@git.koha-community.org> Date: Sun, Nov 14, 2010 at 9:22 PM Subject: [koha-commits] main Koha release repository branch, master, updated. v3.02.00-188-g4b69538 To: koha-commits@lists.koha-community.org This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "main Koha release repository". The branch, master has been updated via 4b69538f9bf6809126cc404a7bc09b02c3830328 (commit) via 38360b766c32ab89c6e5ee87d2459692b47f2b29 (commit) from c0272a6b66e053a86010c7eb8fce1bf080bf428b (commit) Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below. - Log ----------------------------------------------------------------- ----------------------------------------------------------------------- Summary of changes: admin/aqbudgetperiods.pl | 4 +++- admin/aqbudgets.pl | 4 +++- admin/aqplan.pl | 5 +++-- .../prog/en/includes/budgets-active-currency.inc | 1 + .../prog/en/modules/admin/aqbudgetperiods.tmpl | 4 +++- .../prog/en/modules/admin/aqbudgets.tmpl | 6 +++--- .../prog/en/modules/admin/aqplan.tmpl | 2 +- .../prog/en/modules/virtualshelves/shelves.tmpl | 6 +++++- koha-tmpl/opac-tmpl/prog/en/css/opac.css | 5 ++++- .../opac-tmpl/prog/en/modules/opac-shelves.tmpl | 3 ++- 10 files changed, 28 insertions(+), 12 deletions(-) create mode 100644 koha-tmpl/intranet-tmpl/prog/en/includes/budgets-active-currency.inc hooks/post-receive -- main Koha release repository _______________________________________________ koha-commits mailing list koha-commits@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-commits
Hi, On Fri, Nov 26, 2010 at 10:23 AM, Nicole Engard <nengard@gmail.com> wrote:
I think this was brought up before but how do I know what has changed in these files? Commit emails that tell me bug numbers and a short title/summary are much more helpful than this. I use these emails to determine what to update in the manual and I can't keep track if I have to go hunt down these commit numbers. Is there another way to format these types of messages to look like the ones that include details about each patch?
I suggest using an RSS feed: http://git.koha-community.org/gitweb/?p=koha.git;a=rss [master branch] http://git.koha-community.org/gitweb/?p=koha.git;a=rss;h=refs/heads/3.2.x [3.2.x] Regards, Galen -- Galen Charlton gmcharlt@gmail.com
Is that your way of saying it's not possible to get this in the email? Nicole On Fri, Nov 26, 2010 at 10:34 AM, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
On Fri, Nov 26, 2010 at 10:23 AM, Nicole Engard <nengard@gmail.com> wrote:
I think this was brought up before but how do I know what has changed in these files? Commit emails that tell me bug numbers and a short title/summary are much more helpful than this. I use these emails to determine what to update in the manual and I can't keep track if I have to go hunt down these commit numbers. Is there another way to format these types of messages to look like the ones that include details about each patch?
I suggest using an RSS feed:
http://git.koha-community.org/gitweb/?p=koha.git;a=rss [master branch]
http://git.koha-community.org/gitweb/?p=koha.git;a=rss;h=refs/heads/3.2.x [3.2.x]
Regards,
Galen -- Galen Charlton gmcharlt@gmail.com
PS. I used to do the RSS feed and the emails were much easier to go through than the feed because it was everything in one email instead of having to click through 50 commit messages. There was another reason I didn't like the RSS feed, but I don't remember what it was. On Fri, Nov 26, 2010 at 10:51 AM, Nicole Engard <nengard@gmail.com> wrote:
Is that your way of saying it's not possible to get this in the email?
Nicole
On Fri, Nov 26, 2010 at 10:34 AM, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
On Fri, Nov 26, 2010 at 10:23 AM, Nicole Engard <nengard@gmail.com> wrote:
I think this was brought up before but how do I know what has changed in these files? Commit emails that tell me bug numbers and a short title/summary are much more helpful than this. I use these emails to determine what to update in the manual and I can't keep track if I have to go hunt down these commit numbers. Is there another way to format these types of messages to look like the ones that include details about each patch?
I suggest using an RSS feed:
http://git.koha-community.org/gitweb/?p=koha.git;a=rss [master branch]
http://git.koha-community.org/gitweb/?p=koha.git;a=rss;h=refs/heads/3.2.x [3.2.x]
Regards,
Galen -- Galen Charlton gmcharlt@gmail.com
Le 26/11/2010 16:55, Nicole Engard a écrit :
PS. I used to do the RSS feed and the emails were much easier to go through than the feed because it was everything in one email instead of having to click through 50 commit messages. There was another reason I didn't like the RSS feed, but I don't remember what it was. I fully agree with Nicole : it's very handy to have everything in the mail ! (Nicole, it's me that asked, and got the RSS Answer)
cheers -- Paul POULAIN http://www.biblibre.com Expert en Logiciels Libres pour l'info-doc Tel : (33) 4 91 81 35 08
Hi, On Fri, Nov 26, 2010 at 11:02 AM, Paul Poulain <paul.poulain@biblibre.com> wrote:
I fully agree with Nicole : it's very handy to have everything in the mail ! (Nicole, it's me that asked, and got the RSS Answer)
There are quite a few services and software packages that can convert RSS feeds to email. Jes' saying. :) That said, if somebody wants to go to the trouble of finding or writing a git post-receive hook to send emails that are more to your liking, go for it. I'll install it if it seems reasonable. Just keep in mind that it will need to notify on branch creation, not just send email for patches that get pushed to master, 3.2.x, and 3.0.x. Regards, Galen -- Galen Charlton gmcharlt@gmail.com
Galen, It had to do with what was published to the feed versus what was published in the emails - it wasn't the same so getting those as emails isn't helpful. I'm off to subscribe anyway to see if things are different - that said it doesn't help me with all the commits I'm behind on - any tips on using this message to find out what exactly was pushed? I'm 100 commits behind when it comes to the manual. Nicole On Fri, Nov 26, 2010 at 11:31 AM, Galen Charlton <gmcharlt@gmail.com> wrote:
Hi,
On Fri, Nov 26, 2010 at 11:02 AM, Paul Poulain <paul.poulain@biblibre.com> wrote:
I fully agree with Nicole : it's very handy to have everything in the mail ! (Nicole, it's me that asked, and got the RSS Answer)
There are quite a few services and software packages that can convert RSS feeds to email. Jes' saying. :)
That said, if somebody wants to go to the trouble of finding or writing a git post-receive hook to send emails that are more to your liking, go for it. I'll install it if it seems reasonable. Just keep in mind that it will need to notify on branch creation, not just send email for patches that get pushed to master, 3.2.x, and 3.0.x.
Regards,
Galen -- Galen Charlton gmcharlt@gmail.com _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org http://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
participants (3)
-
Galen Charlton -
Nicole Engard -
Paul Poulain