Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Many thanks Phil. Let's wait for the first commit to appear. Brgds, Viktor On Thu, Jan 29, 2009 at 9:25 AM, Phil Barnett wrote: > Viktor Szakáts wrote: > >> Hi Phil, >> >> >>Yes, that looks like it. >> >>I can build mailboxes on the domain and I can forward them. I can >>join h

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Viktor Szakáts wrote: Hi Phil, Yes, that looks like it. I can build mailboxes on the domain and I can forward them. I can join harbour@harbour-project.org with the nomail option set. Does that sound like it will work? nomail means d

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Hi Phil, > Again, our other, much simpler and consistent option is to simply swap the >> manual mails to automated ones, with no change on any parties side. >> > Ok, that was a very coherent discussion that adds meaning that you were not > conveying before. Thank you. > > Earlier, it was requeste

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Viktor Szakáts wrote: >Anyhow I feel this will lead to a mess, where some ppl don't get informed about changes, because not being subscribed to the other list, and because of this, some developers will continue to send manual ChangeLogs, creating double notifications for those who subscribed.

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Hi Phil, > I've offered to give you: > > 1. If you reply to these messages, the reply goes to the developer list. > 2. By adding one rule in your email system, you can have them delivered to > the same developer folder that you already have. > > How is that not exactly what you want? I mean, if i

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Viktor Szakáts wrote: Hi Phil, What is the problem with my proposal? You are creating a feed to the mail system that there is no way to opt out of, thus giving regular subscribers no way to reduce their mail burden. Sure you can filter i away, but only after you have

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Hi Phil, > What is the problem with my proposal? >> > You are creating a feed to the mail system that there is no way to opt out > of, thus giving regular subscribers no way to reduce their mail burden. Sure > you can filter i away, but only after you have downloaded it. And it's going > to have

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Viktor Szakáts wrote: Not very good. Since you _must_ subscribe to and monitor yet another list, even if you just want to be informed about the changes, just like before. What is the problem with my proposal? You are creating a feed to the mail system that there is no way to opt out of, thu

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

> > IMO this is a developer list so such mails are expected, if we split the >> lists into two, it will be complicated (and error prone) to simply reply to >> those commit e-mails (this is very useful and also common practice), which >> kind of defeats the purpose, as the manual ChangeLog e-mails w

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Viktor Szakáts wrote: IMO this is a developer list so such mails are expected, if we split the lists into two, it will be complicated (and error prone) to simply reply to those commit e-mails (this is very useful and also common practice), which kind of defeats the purpose, as the manual Chang

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

IMO this is a developer list so such mails are expected, if we split the lists into two, it will be complicated (and error prone) to simply reply to those commit e-mails (this is very useful and also common practice), which kind of defeats the purpose, as the manual ChangeLog e-mails would still ha

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

On Wed, 21 Jan 2009, Phil Barnett wrote: Hi Phil, > I think it would be better to create a mailing list for these svn mails > that anyone can subscribe to and it will be read only except for the SVN > mailer. That way, it will not inflate the developer list with messages that > a lot of people

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Mindaugas Kavaliauskas wrote: Viktor Szakáts wrote: Maybe some sort of forwarder e-mail address could do the job. Mmmm... Yes, perhaps. I'm nor shure if mailling list has possibility to allow *...@sourceforge.net users. Otherwise every "sourceforge.net developer" one by one should be added

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Phil, could you please also raise the message size limit to 150K? sf.net has a '--max-diff-length 10' option set, so 150K is enough, and it's also acceptable as a generic limit for all subscribers. (we're at 40K right now AFAIK). Brgds, Viktor On Sat, Jan 17, 2009 at 11:50 AM, Viktor Szakáts

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Hi Phil, > >> Yes, that looks like it. >> > I can build mailboxes on the domain and I can forward them. I can join > harbour@harbour-project.org with the nomail option set. > > Does that sound like it will work? nomail means don't send any list mail. Sounds okay, let's try it with svncom...@harb

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Viktor Szakáts wrote: Mmmm... Yes, perhaps. I'm nor shure if mailling list has possibility to allow *...@sourceforge.net users. Otherwise every "sourceforge.net developer" one by one should be added to list. This can have also

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Well, we have option for both. It diff is problematic, we can easily have notifications without it. With diff, we also need to deal with maximum message sizes, which is 40K. Diff files can often be larger than that. We can raise the limit (maybe only for the forwarder mailbox), or omit the diffs.

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Hi, Il 16/01/2009 16.38, Mindaugas Kavaliauskas ha scritto: Log Message: --- testing hook Log message is HERE , at the begining of email, so you don't have to look all content of email. Sometimes, I use to see changes of other developers, so diff output is usefull. Perhaps, the

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

> > Mmmm... Yes, perhaps. I'm nor shure if mailling list has possibility to > allow *...@sourceforge.net users. Otherwise every "sourceforge.net developer" > one by one should be added to list. > This can have also have some side effects, if someone uses redirection from > @sourceforge.net account,

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

There is option in sf.net to add multiple hooks, so there could be one hook with and another without the diffs. I personally wouldn't make it that complicated, as the main point of this list is development, so diffs shouldn't be something unorthodox or inappropriate here, at least IMO. Brgds, Vikt

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

The other question is that, AFAIR and for description I have read, svnnotify will send every commit made to any file on SVN and not only to changelog file, as implemented on sf.net, and this I don't like. Hi, From: [vszakats users sourceforge net] Date: Fri, Jan 16, 2009 at 12:26 PM Subject:

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Viktor Szakáts wrote: Maybe some sort of forwarder e-mail address could do the job. Mmmm... Yes, perhaps. I'm nor shure if mailling list has possibility to allow *...@sourceforge.net users. Otherwise every "sourceforge.net developer" one by one should be added to list. This can have also hav

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

> > Maybe some sort of forwarder e-mail address could do the job. >> >> As I have seen in sf.net docs the only option is: > "we only support one user-provided option to this script, the email address > to send the notification to" > so email will be sent using sf login name. > This can be solved i

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Hi Viktor, Il 16/01/2009 15.06, Viktor Szakáts ha scritto: I'm not sure how svnnotify works, but if it's a client side solution, we haven't solved too much (the point would be to make this fully automatic for everyone), if it's server side, the choices are limited to the sf.net

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

I'm not sure how svnnotify works, but if it's a client side solution, we haven't solved too much (the point would be to make this fully automatic for everyone), if it's server side, the choices are limited to the sf.net hosted notifier script, and with this, the only configuration option is a desti

Re: [Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

Viktor Szakáts wrote: Any ideas how to resolve that the best way? Hi, svnnotify --from somewh...@example.com Regards, Mindaugas ___ Harbour mailing list Harbour@harbour-project.org http://lists.harbour-project.org/mailman/listinfo/harbour

[Harbour] Fwd: SF.net SVN: harbour-project:[10057] trunk/harbour/ChangeLog

This is how such e-mail looks like. It looks fine to me. Now, the problem is, the sender e-mail address is always the committer's sf.net e-mail alias, and our mailing list allows only members to post (rightly so), which means that we cannot set the mailing list address as recipient, since mails wil