On Wed, 25 Jan 2012 16:09:53 +
Nick Treleaven wrote:
> On 22/01/2012 15:50, Enrico Tröger wrote:
> >> > Ok, so I'll change the hook at Github soon and we get some kind
> >> > of live test:).
> > Done.
> > Any new commit mails will be sent from the script (which I will
> > publish in some rep
On 22/01/2012 15:50, Enrico Tröger wrote:
> Ok, so I'll change the hook at Github soon and we get some kind of live
> test:).
Done.
Any new commit mails will be sent from the script (which I will publish
in some repository).
Just pushed two commits - they got split into two mails and include
On 21/01/12 11:38, Enrico Tröger wrote:
> On Fri, 20 Jan 2012 19:54:17 +0100, Colomban wrote:
>
>> Le 15/01/2012 23:53, Enrico Tröger a écrit :
>>> On Sun, 15 Jan 2012 13:35:35 -0800, Matthew wrote:
>>>
On 01/15/2012 12:03 PM, Lex Trotman wrote:
> [...]
>> What do you think?
>>
>>
On Fri, 20 Jan 2012 19:54:17 +0100, Colomban wrote:
>Le 15/01/2012 23:53, Enrico Tröger a écrit :
>> On Sun, 15 Jan 2012 13:35:35 -0800, Matthew wrote:
>>
>>> On 01/15/2012 12:03 PM, Lex Trotman wrote:
[...]
> What do you think?
>
> If we agree to change the commit mails to this f
Le 15/01/2012 23:53, Enrico Tröger a écrit :
On Sun, 15 Jan 2012 13:35:35 -0800, Matthew wrote:
On 01/15/2012 12:03 PM, Lex Trotman wrote:
[...]
What do you think?
If we agree to change the commit mails to this format, I'd deploy
the script soon.
I'd very much like it, and I'm fine with t
On Sun, 15 Jan 2012 13:35:35 -0800, Matthew wrote:
>On 01/15/2012 12:03 PM, Lex Trotman wrote:
>> [...]
>>> What do you think?
>>>
>>> If we agree to change the commit mails to this format, I'd deploy
>>> the script soon.
>>>
>>
>> Hi Enrico,
>>
>> Actually I've become used to the standard github
On 01/15/2012 12:03 PM, Lex Trotman wrote:
[...]
What do you think?
If we agree to change the commit mails to this format, I'd deploy the
script soon.
Hi Enrico,
Actually I've become used to the standard github commit emails and
clicking on the link for the diff.
Especially for large chang
[...]
> What do you think?
>
> If we agree to change the commit mails to this format, I'd deploy the
> script soon.
>
Hi Enrico,
Actually I've become used to the standard github commit emails and
clicking on the link for the diff.
Especially for large changes like geany.html or geany.glade (desp
On Wed, 02 Nov 2011 19:20:57 +0100, Colomban wrote:
>> So I take this as a 'yes, turn it into something more similar to the
>> old SVN commit mails with diff, size-limited and a link to the web
>> repo'.
>> Will do this soon and announce it before and after.
>
>Just wanted to say: looking forward
Le 02/11/2011 18:18, Enrico Tröger a écrit :
> On Mon, 31 Oct 2011 15:29:08 -0700, Matthew wrote:
>
>> On 10/31/2011 09:44 AM, Nick Treleaven wrote:
>>> On 31/10/2011 15:07, Nick Treleaven wrote:
On 31/10/2011 13:57, Matthew Brush wrote:
I'm not sure we would see a flood on a merge,
On Mon, 31 Oct 2011 15:29:08 -0700, Matthew wrote:
>On 10/31/2011 09:44 AM, Nick Treleaven wrote:
>> On 31/10/2011 15:07, Nick Treleaven wrote:
>>> On 31/10/2011 13:57, Matthew Brush wrote:
>>> I'm not sure we would see a flood on a merge, probably only one
>>> commit saying 'merged gtkbui
On 10/31/2011 09:44 AM, Nick Treleaven wrote:
On 31/10/2011 15:07, Nick Treleaven wrote:
On 31/10/2011 13:57, Matthew Brush wrote:
I'm not sure we would see a flood on a merge, probably only one
commit saying 'merged gtkbuilder branch'? The gtkbuilder commits
should appear as they are committed
On Mon, 31 Oct 2011 16:44:52 +
Nick Treleaven wrote:
> On 31/10/2011 15:07, Nick Treleaven wrote:
> > On 31/10/2011 13:57, Matthew Brush wrote:
> > I'm not sure we would see a flood on a merge, probably only one
> > commit saying 'merged gtkbuilder branch'? The gtkbuilder commits
> >>
On 31/10/2011 15:07, Nick Treleaven wrote:
On 31/10/2011 13:57, Matthew Brush wrote:
I'm not sure we would see a flood on a merge, probably only one
commit saying 'merged gtkbuilder branch'? The gtkbuilder commits
should appear as they are committed, not on merge.
I think when you merge it ma
On 31/10/2011 13:57, Matthew Brush wrote:
I'm not sure we would see a flood on a merge, probably only one
commit saying 'merged gtkbuilder branch'? The gtkbuilder commits
should appear as they are committed, not on merge.
I think when you merge it makes all the commits onto the branch that
was
On 10/31/2011 06:45 AM, Frank Lanitz wrote:
On Mon, 31 Oct 2011 06:29:36 -0700
Matthew Brush wrote:
On 11-10-31 05:00 AM, Nick Treleaven wrote:
On 25/10/2011 00:33, Lex Trotman wrote:
[...]
If we go back to individual commit mails with diffs, is there
anyway to limit how many individual mes
On Mon, 31 Oct 2011 06:29:36 -0700
Matthew Brush wrote:
> On 11-10-31 05:00 AM, Nick Treleaven wrote:
> > On 25/10/2011 00:33, Lex Trotman wrote:
> >> [...]
> >>> If we go back to individual commit mails with diffs, is there
> >>> anyway to limit how many individual messages get sent out at once
On 11-10-31 05:00 AM, Nick Treleaven wrote:
On 25/10/2011 00:33, Lex Trotman wrote:
[...]
If we go back to individual commit mails with diffs, is there anyway to
limit how many individual messages get sent out at once and how many
lines
can be in a diff? Ex. if we merge the gtkbuilder branch at
On 25/10/2011 00:33, Lex Trotman wrote:
[...]
If we go back to individual commit mails with diffs, is there anyway to
limit how many individual messages get sent out at once and how many lines
can be in a diff? Ex. if we merge the gtkbuilder branch at some point, is
there anyway to prevent from
On Tue, 18 Oct 2011 20:03:09 +0200
Colomban Wendling wrote:
> > For example, the Xfce guys have a simple Shell script to do the job
> > and it does it as I would wish:
> > http://git.xfce.org/admin/xfce-git-hooks/tree/hooks/update-03-send-commit-mails
> >
> > An example mail:
> > http://mail.xfc
Am 25.10.2011 01:23, schrieb Matthew Brush:
I do like having the diffs in the mails normally, but I also don't
much mind clicking a hyperlink to see a well coloured and laid out diff.
I'd actually prefer clicking+colored over in-mail.
OTOH I couldn't care less because I'm not subscribed to th
[...]
> If we go back to individual commit mails with diffs, is there anyway to
> limit how many individual messages get sent out at once and how many lines
> can be in a diff? Ex. if we merge the gtkbuilder branch at some point, is
> there anyway to prevent from flooding the list with all those c
On 10/24/2011 02:45 PM, Enrico Tröger wrote:
On Tue, 18 Oct 2011 20:03:09 +0200, Colomban wrote:
Le 18/10/2011 19:52, Enrico Tröger a écrit :
Hey guys,
right now, we use the stock email commit hook from Github and let it
send commit mails to the geany-commits mailing list.
However, compared
Am Montag, den 24.10.2011, 23:45 +0200 schrieb Enrico Tröger:
> >Nothing but a big "+1" ;)
+1
--
Dominic Hopf
http://dominichopf.de/
Key Fingerprint: A7DF C4FC 07AE 4DDC 5CA0 BD93 AAB0 6019 CA7D 868D
signature.asc
Description: This is a digitally signed message part
_
On Tue, 18 Oct 2011 20:03:09 +0200, Colomban wrote:
>Le 18/10/2011 19:52, Enrico Tröger a écrit :
>> Hey guys,
>>
>>
>> right now, we use the stock email commit hook from Github and let it
>> send commit mails to the geany-commits mailing list.
>>
>> However, compared to the old Subversion comm
On Tue, 18 Oct 2011 20:03:09 +0200, Colomban wrote:
>Le 18/10/2011 19:52, Enrico Tröger a écrit :
>> Hey guys,
>>
>>
>> right now, we use the stock email commit hook from Github and let it
>> send commit mails to the geany-commits mailing list.
>>
>> However, compared to the old Subversion comm
Le 18/10/2011 19:52, Enrico Tröger a écrit :
> Hey guys,
>
>
> right now, we use the stock email commit hook from Github and let it
> send commit mails to the geany-commits mailing list.
>
> However, compared to the old Subversion commit mails, they are quite
> different:
>
> First, they are no
Hey guys,
right now, we use the stock email commit hook from Github and let it
send commit mails to the geany-commits mailing list.
However, compared to the old Subversion commit mails, they are quite
different:
First, they are not really commit mails but rather "push" mails, that
is all commit
28 matches
Mail list logo
