Re: New Email Scripts

Richard Heck wrote: > On 06/03/2013 03:27 PM, Pavel Sanda wrote: >> Richard Heck wrote: >>> a look, I've attached it. I'm not sure why it would be base64. >> If you look on the header of cvs-list mails do you see this line: >> Content-Transfer-Encoding: base64 > > Yes, I see it now, and the source

Re: New Email Scripts

On 06/03/2013 03:27 PM, Pavel Sanda wrote: Richard Heck wrote: a look, I've attached it. I'm not sure why it would be base64. If you look on the header of cvs-list mails do you see this line: Content-Transfer-Encoding: base64 Yes, I see it now, and the source of the message looks weird, too.

Re: New Email Scripts

Richard Heck wrote: > a look, I've attached it. I'm not sure why it would be base64. If you look on the header of cvs-list mails do you see this line: Content-Transfer-Encoding: base64 ? Pavel

Re: New Email Scripts

On 06/03/2013 03:16 PM, Pavel Sanda wrote: Pavel Sanda wrote: (new mails are encapsulated in base64 encoding that's why coloring works). Actually no, I seem to be fooled by my own scripts ;) Why do you use base64 encoding? Can't we continue with plain text version of the mails? I didn't know

Re: New Email Scripts

Pavel Sanda wrote: > (new mails are encapsulated in base64 encoding that's why coloring works). Actually no, I seem to be fooled by my own scripts ;) Why do you use base64 encoding? Can't we continue with plain text version of the mails? Pavel

Re: New Email Scripts

Richard Heck wrote: > There seemed to be a sense that we shouldn't send multiple emails for a > single push in gsoc and featrues. I agree. I was merely talking about output format, not frequency of sending (new mails are encapsulated in base64 encoding that's why coloring works). If it's complica

Re: New Email Scripts

Richard Heck wrote: > It should now be working. Everything is configurable, so let me know if > something isn't the way you'd like it to be. Nice. How hard is to synchronize output format for scripts used in different repos like GSoC? I use specific processing for lyx-cvs mails and having two dif

Re: New Email Scripts

On 06/03/2013 02:32 PM, Pavel Sanda wrote: Richard Heck wrote: It should now be working. Everything is configurable, so let me know if something isn't the way you'd like it to be. Nice. How hard is to synchronize output format for scripts used in different repos like GSoC? I use specific proce

Re: New Email Scripts

On 06/03/2013 04:54 AM, Vincent van Ravesteijn wrote: On Mon, Jun 3, 2013 at 10:41 AM, Pavel Sanda > wrote: Vincent van Ravesteijn wrote: > Maybe, it is not that useful to send a mail to everyone for each commit in > the gsoc repo. I hope the students wi

Re: New Email Scripts

Vincent van Ravesteijn wrote: > I proposed to my student to work in feature branches in the gsoc repo. When > something is sort of ready, it is merged into the gsoc/outliner/master > branch. When gsoc/outliner/master has acquired enough to be usable by the > general public, it can be merged into ly

Re: New Email Scripts

Vincent van Ravesteijn wrote: > If we make the script such that all updates to a certain branch sends an > e-mail that is part of the same e-mail thread, it might be much more > comfortable for the recipient... if the recipient chose to use a suitable > mail client. > > Would that be a good idea ?

Re: New Email Scripts

Oh.. and something that I proposed a long time ago. If we make the script such that all updates to a certain branch sends an e-mail that is part of the same e-mail thread, it might be much more comfortable for the recipient... if the recipient chose to use a suitable mail client. Would that be a

Re: New Email Scripts

On Mon, Jun 3, 2013 at 10:41 AM, Pavel Sanda wrote: > Vincent van Ravesteijn wrote: > > Maybe, it is not that useful to send a mail to everyone for each commit > in > > the gsoc repo. I hope the students will commit and push frequently, so > the > > mentors can see what they are doing. > > It mea

Re: New Email Scripts

Vincent van Ravesteijn wrote: > Maybe, it is not that useful to send a mail to everyone for each commit in > the gsoc repo. I hope the students will commit and push frequently, so the > mentors can see what they are doing. It means that GSOC work would be visible through mail-diffs only at the f

Re: New Email Scripts

On 06/01/2013 12:02 AM, Scott Kostyshak wrote: On Fri, May 31, 2013 at 10:03 AM, Richard Heck wrote: On 05/31/2013 01:58 AM, Vincent van Ravesteijn wrote: It looks like the title is culled: "installer: prepare for a LyX 2" instead of "installer: prepare for a LyX 2.1beta release". Yes. Using

Re: New Email Scripts

On Fri, May 31, 2013 at 10:03 AM, Richard Heck wrote: > On 05/31/2013 01:58 AM, Vincent van Ravesteijn wrote: > >> It looks like the title is culled: "installer: prepare for a LyX 2" >> instead of "installer: prepare for a LyX 2.1beta release". > > Yes. Using the entire title seemed ill advised. B

Re: New Email Scripts

On 05/31/2013 01:58 AM, Vincent van Ravesteijn wrote: On Fri, May 31, 2013 at 4:16 AM, Richard Heck > wrote: After the push of the kill-gettext branch, I decided that I needed to do something about the email scripts, so that multiple commits would generate

Re: New Email Scripts

Op 31-5-2013 4:16, Richard Heck schreef: After the push of the kill-gettext branch, I decided that I needed to do something about the email scripts, so that multiple commits would generate multiple emails. I've now done this. The downside is that there have been a lot of random commit message

Re: New Email Scripts

On Fri, May 31, 2013 at 4:16 AM, Richard Heck wrote: > > After the push of the kill-gettext branch, I decided that I needed to do > something about the email scripts, so that multiple commits would generate > multiple emails. I've now done this. The downside is that there have been a > lot of ran

New Email Scripts

After the push of the kill-gettext branch, I decided that I needed to do something about the email scripts, so that multiple commits would generate multiple emails. I've now done this. The downside is that there have been a lot of random commit messages, as I tested to get it working. I did t