From: Yuval L. <sf...@sf...> - 2011-02-20 18:47:40
|
Repository Email Notification has been fixed for all Hugin, Enblend, Panotools repositories. Thank you for your patience. Yuv |
From: dmg <dm...@uv...> - 2011-02-20 21:57:25
|
Thanks Yuv, this is much appreciated. --dmg 2011/2/20 Yuval Levy <sf...@sf...>: > Repository Email Notification has been fixed for all Hugin, Enblend, Panotools > repositories. > > Thank you for your patience. > Yuv > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > PanoTools-devel mailing list > Pan...@li... > https://lists.sourceforge.net/lists/listinfo/panotools-devel > > -- --dmg --- Daniel M. German http://turingmachine.org |
From: Jim W. <jwa...@ph...> - 2011-02-20 22:22:01
|
On 2011-02-20 2:47 PM, Yuval Levy wrote: > Repository Email Notification has been fixed for all Hugin, Enblend, Panotools > repositories. Thank you. I have received a couple of messages. The first 40 lines or so look fine but then turns to gibberish. Looking at the patches doing a Incoming I see that the entire patch is in the email but then there is a bunch of gibberish. -- Jim Watters http://photocreations.ca |
From: Yuval L. <sf...@sf...> - 2011-02-21 01:11:33
|
On February 20, 2011 05:21:50 pm Jim Watters wrote: > On 2011-02-20 2:47 PM, Yuval Levy wrote: > > Repository Email Notification has been fixed for all Hugin, Enblend, > > Panotools repositories. > > Thank you. I have received a couple of messages. The first 40 lines or so > look fine but then turns to gibberish. I saw something similar too and I am at loss. I did not find any corruption in the repo, which is what counts. The delivery method changed - previously it was SMTP while now it is via sendmail. Maybe something happens in between. SMTP still does not work on SourceForge. I am tempted to experiment with an external SMTP server that I do have control of but I have no time and quite frankly I would not like to leave credentials to use my SMTP server in a SourceForge configuration file since it would make it an open relay to everybody who has access to that configuration file (e.g. hackers that attack SF). Will have a look over the next few weeks / months and if the problem persist I will look into it / report to SF. I wish the SMTP method would still work. Yuv > > Looking at the patches doing a Incoming I see that the entire patch is in > the email but then there is a bunch of gibberish. |
From: Jim W. <jwa...@ph...> - 2011-02-24 03:13:55
|
> Repository Email Notification has been fixed Is there a way to push several commits as one set of changes instead of each commit showing up as a seperate change? Also I see that the that each commit after a push is sent out as an email. Those emails are in reverse order to how they were committed. Or at least for me. It does make it hard to follow. -- Jim Watters http://photocreations.ca |
From: Yuval L. <sf...@sf...> - 2011-02-24 04:02:16
|
On February 23, 2011 10:13:42 pm Jim Watters wrote: > > Repository Email Notification has been fixed > > Is there a way to push several commits as one set of changes instead of > each commit showing up as a seperate change? I am not sure I understand the question. The whole point of having an SCM is to record separate changes? when you commit, you commit only locally. When you push, you push all those commits to the central repository in one go. I think there is some extension somewhere to "collapse" all of your commits into a single one before pushing, to "hide" your small steps and make it one big one for the central repo. But I do not like the idea. > Also I see that the that each commit after a push is sent out as an email. > Those emails are in reverse order to how they were committed. Or at least > for me. It does make it hard to follow. the emails are sent in appropriate order to sendmail, but how the queue is managed there; and then in the SMTP server; and then at your ISP; is beyond the control of the repository. Especially when pushing a number of changes at the same time. I could limit the email to once per group of changesets (rather than once per commit), but this would make the emails much less informative. At the moment I have an issue with the emails not showing the commit log message. Not sure where this happens. I had to log on the web to read your commit log messages. Nobody has commented on the further migration from SVN to Hg. I guess I will have to volunteer and do it. I'd like to first get the first beta of Hugin out the door. Sometimes in March I should find the time to migrate all what is in SVN into Hg, like I did for Hugin a year ago. Yuv |