You can subscribe to this list here.
2003 |
Jan
|
Feb
(17) |
Mar
(42) |
Apr
(6) |
May
(7) |
Jun
(30) |
Jul
(9) |
Aug
(75) |
Sep
(30) |
Oct
(2) |
Nov
(21) |
Dec
(16) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2004 |
Jan
|
Feb
(22) |
Mar
(2) |
Apr
(15) |
May
|
Jun
(2) |
Jul
|
Aug
(7) |
Sep
(5) |
Oct
(3) |
Nov
(1) |
Dec
(1) |
2005 |
Jan
|
Feb
(3) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(1) |
Aug
|
Sep
(5) |
Oct
|
Nov
|
Dec
|
2006 |
Jan
|
Feb
(3) |
Mar
(7) |
Apr
(1) |
May
(1) |
Jun
(2) |
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
(2) |
Dec
|
2007 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2009 |
Jan
|
Feb
|
Mar
|
Apr
(2) |
May
(2) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(1) |
Dec
|
2012 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
|
Dec
|
2013 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(4) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2014 |
Jan
|
Feb
|
Mar
|
Apr
(3) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Martin P. <mb...@so...> - 2014-04-24 01:51:27
|
Hi Milind, If you can separate those changes out into things that are generally applicable (ie they won't break the build elsewhere), I would be happy to merge them in. Or if you aren't sure how to do that, put up a pull request anyhow and we can talk about it. Thanks Martin On 23 April 2014 23:49, Milind Gupta <mil...@gm...> wrote: > Hi Martin, > Thanks for the update. Just last week I compiled librsync as a > dll from the sourceforge page on windows using Code::Blocks. I have made a > Code::Blocks project for the dll. If you want I can send that to you to add > for the PC build. Since Code::Blocks is cross platform I think the same > project should work on other platforms as well. I had tried cygwin and > Visual Studio express 2013 but nothing worked for me. For Codeblocks I had > to make a change in the snprintf.c file. I had to comment the #define > HAVE_VARARGS_H line and add the line #define HAVE_STDARG_H otherwise it > gives errors. After that I was able to generate tne use the dll properly. > > Thanks, > Milind > > > On Tue, Apr 22, 2014 at 9:44 PM, Martin Pool <mb...@so...> wrote: > >> Hi all, >> >> I've made a new home for librsync in < >> https://github.com/librsync/librsync>. Pretty nice to see it's still >> useful and used after 14 years! >> >> I'd like to maintain librsync a little more actively again, starting by >> getting a clean build on modern compilers, seeing what new tests can be >> added, and merging patches people have done elsewhere. I hope to make a new >> release in the next month or so. If you've fixed bugs in your own fork, >> please do get in touch on lib...@go... >> >> I am also going to migrate the lists from Sourceforge to Google Groups >> partly for the sake of better spam/moderation management: >> >> https://groups.google.com/forum/#!forum/librsync >> https://groups.google.com/forum/#!forum/librsync-announce >> >> -- >> Martin >> >> >> ------------------------------------------------------------------------------ >> Start Your Social Network Today - Download eXo Platform >> Build your Enterprise Intranet with eXo Platform Software >> Java Based Open Source Intranet - Social, Extensible, Cloud Ready >> Get Started Now And Turn Your Intranet Into A Collaboration Platform >> http://p.sf.net/sfu/ExoPlatform >> _______________________________________________ >> librsync-users mailing list >> lib...@li... >> https://lists.sourceforge.net/lists/listinfo/librsync-users >> >> > -- > You received this message because you are subscribed to the Google Groups > "librsync" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to lib...@go.... > For more options, visit https://groups.google.com/d/optout. > -- Martin |
From: Martin P. <mb...@so...> - 2014-04-23 04:45:40
|
Hi all, I've made a new home for librsync in <https://github.com/librsync/librsync>. Pretty nice to see it's still useful and used after 14 years! I'd like to maintain librsync a little more actively again, starting by getting a clean build on modern compilers, seeing what new tests can be added, and merging patches people have done elsewhere. I hope to make a new release in the next month or so. If you've fixed bugs in your own fork, please do get in touch on lib...@go... I am also going to migrate the lists from Sourceforge to Google Groups partly for the sake of better spam/moderation management: https://groups.google.com/forum/#!forum/librsync https://groups.google.com/forum/#!forum/librsync-announce -- Martin |
From: Martin P. <mb...@so...> - 2014-04-21 05:21:43
|
Hi Paul! Quite a while since your message, but I finally got around to making a `librsync` organization. If you would like to transfer your import across to that organization, that would be great. https://github.com/librsync On 16 May 2013 18:18, Paul Oppenheim <pa...@ge...> wrote: > Quite a day for librsync; > > I went through the process to import librsync (with revision history > from CVS) into git. Hopefully someone finds this useful: > https://github.com/pauloppenheim-liveloop/librsync > > I have also released a fork which includes patches for a Windows build > using Microsoft Visual Studio 2008: > https://github.com/pauloppenheim-liveloop/librsync-winbuild > > There appear to be a number of projects using librsync still: > https://github.com/search?q=librsync&type=Repositories > > Coincidentally, also released today, a fork by Dropbox (lacking proper > history / patchset export, sadly): > https://github.com/dropbox/librsync > > so, thanks for the library! > > + paul > > > ------------------------------------------------------------------------------ > AlienVault Unified Security Management (USM) platform delivers complete > security visibility with the essential security capabilities. Easily and > efficiently configure, manage, and operate all of your security controls > from a single console and one unified framework. Download a free trial. > http://p.sf.net/sfu/alienvault_d2d > _______________________________________________ > librsync-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/librsync-devel > -- Martin |
From: Martin P. <mb...@so...> - 2013-05-16 10:42:42
|
github is fine. No need to worry about ownership or the name mapping right now - I will have a look later. On 16 May 2013 19:10, Paul Oppenheim <pa...@ge...> wrote: > Hi Martin, > > You're welcome! I would be happy to add you as an owner or just > transfer the repo to your github account - it's your code after all! > Being a dvcs, there's also nothing stopping you from just taking this > import and moving it to sourceforge - or launchpad? I could also do a > different conversion with different username -> email mappings if you > prefer, i've got a working config now. > > + paul > > On Thu, May 16, 2013 at 1:48 AM, Martin Pool <mb...@so...> wrote: > > Hi, Paul, > > > > Thanks for doing a conversion and for posting. I had been thinking about > > moving the official home to github and making a new release with whatever > > patches can be merged. > > > > > > On 16 May 2013 18:18, Paul Oppenheim <pa...@ge...> wrote: > >> > >> Quite a day for librsync; > >> > >> I went through the process to import librsync (with revision history > >> from CVS) into git. Hopefully someone finds this useful: > >> https://github.com/pauloppenheim-liveloop/librsync > >> > >> I have also released a fork which includes patches for a Windows build > >> using Microsoft Visual Studio 2008: > >> https://github.com/pauloppenheim-liveloop/librsync-winbuild > >> > >> There appear to be a number of projects using librsync still: > >> https://github.com/search?q=librsync&type=Repositories > >> > >> Coincidentally, also released today, a fork by Dropbox (lacking proper > >> history / patchset export, sadly): > >> https://github.com/dropbox/librsync > >> > >> so, thanks for the library! > >> > >> + paul > >> > >> > >> > ------------------------------------------------------------------------------ > >> AlienVault Unified Security Management (USM) platform delivers complete > >> security visibility with the essential security capabilities. Easily and > >> efficiently configure, manage, and operate all of your security controls > >> from a single console and one unified framework. Download a free trial. > >> http://p.sf.net/sfu/alienvault_d2d > >> _______________________________________________ > >> librsync-devel mailing list > >> lib...@li... > >> https://lists.sourceforge.net/lists/listinfo/librsync-devel > > > > > > > > > > -- > > Martin > -- Martin |
From: Paul O. <pa...@ge...> - 2013-05-16 09:39:25
|
Hi Martin, You're welcome! I would be happy to add you as an owner or just transfer the repo to your github account - it's your code after all! Being a dvcs, there's also nothing stopping you from just taking this import and moving it to sourceforge - or launchpad? I could also do a different conversion with different username -> email mappings if you prefer, i've got a working config now. + paul On Thu, May 16, 2013 at 1:48 AM, Martin Pool <mb...@so...> wrote: > Hi, Paul, > > Thanks for doing a conversion and for posting. I had been thinking about > moving the official home to github and making a new release with whatever > patches can be merged. > > > On 16 May 2013 18:18, Paul Oppenheim <pa...@ge...> wrote: >> >> Quite a day for librsync; >> >> I went through the process to import librsync (with revision history >> from CVS) into git. Hopefully someone finds this useful: >> https://github.com/pauloppenheim-liveloop/librsync >> >> I have also released a fork which includes patches for a Windows build >> using Microsoft Visual Studio 2008: >> https://github.com/pauloppenheim-liveloop/librsync-winbuild >> >> There appear to be a number of projects using librsync still: >> https://github.com/search?q=librsync&type=Repositories >> >> Coincidentally, also released today, a fork by Dropbox (lacking proper >> history / patchset export, sadly): >> https://github.com/dropbox/librsync >> >> so, thanks for the library! >> >> + paul >> >> >> ------------------------------------------------------------------------------ >> AlienVault Unified Security Management (USM) platform delivers complete >> security visibility with the essential security capabilities. Easily and >> efficiently configure, manage, and operate all of your security controls >> from a single console and one unified framework. Download a free trial. >> http://p.sf.net/sfu/alienvault_d2d >> _______________________________________________ >> librsync-devel mailing list >> lib...@li... >> https://lists.sourceforge.net/lists/listinfo/librsync-devel > > > > > -- > Martin |
From: Martin P. <mb...@so...> - 2013-05-16 08:49:27
|
Hi, Paul, Thanks for doing a conversion and for posting. I had been thinking about moving the official home to github and making a new release with whatever patches can be merged. On 16 May 2013 18:18, Paul Oppenheim <pa...@ge...> wrote: > Quite a day for librsync; > > I went through the process to import librsync (with revision history > from CVS) into git. Hopefully someone finds this useful: > https://github.com/pauloppenheim-liveloop/librsync > > I have also released a fork which includes patches for a Windows build > using Microsoft Visual Studio 2008: > https://github.com/pauloppenheim-liveloop/librsync-winbuild > > There appear to be a number of projects using librsync still: > https://github.com/search?q=librsync&type=Repositories > > Coincidentally, also released today, a fork by Dropbox (lacking proper > history / patchset export, sadly): > https://github.com/dropbox/librsync > > so, thanks for the library! > > + paul > > > ------------------------------------------------------------------------------ > AlienVault Unified Security Management (USM) platform delivers complete > security visibility with the essential security capabilities. Easily and > efficiently configure, manage, and operate all of your security controls > from a single console and one unified framework. Download a free trial. > http://p.sf.net/sfu/alienvault_d2d > _______________________________________________ > librsync-devel mailing list > lib...@li... > https://lists.sourceforge.net/lists/listinfo/librsync-devel > -- Martin |
From: Paul O. <pa...@ge...> - 2013-05-16 08:45:17
|
Quite a day for librsync; I went through the process to import librsync (with revision history from CVS) into git. Hopefully someone finds this useful: https://github.com/pauloppenheim-liveloop/librsync I have also released a fork which includes patches for a Windows build using Microsoft Visual Studio 2008: https://github.com/pauloppenheim-liveloop/librsync-winbuild There appear to be a number of projects using librsync still: https://github.com/search?q=librsync&type=Repositories Coincidentally, also released today, a fork by Dropbox (lacking proper history / patchset export, sadly): https://github.com/dropbox/librsync so, thanks for the library! + paul |
From: Martin P. <mb...@so...> - 2012-10-01 10:35:39
|
Thanks for the patches! I'll review them. |
From: karamjeet s. <ksb...@gm...> - 2011-11-10 08:20:47
|
Hi, I am try to run/compile librsync for my mobile application on mac but not able because librsync shows number of error while I compiling/run librsync on Mac. Thanks Karamjeet Singh -- K@r@m........[:)] |
From: Daniel.Li <dan...@us...> - 2009-05-09 08:53:44
|
On Fri, 2009-05-08 at 13:17 +0100, Donovan Baarda wrote: > On Tue, 2009-04-21 at 13:17 +0800, Daniel.Li wrote: > > Thanks Dave. > > > > I'll study the code first and try to see what I can do with it. :) > > > > On Tue, 2009-04-21 at 14:38 +1000, Dave Kempe wrote: > > > Nope, no one is home. The last patch was the fix the 4gb file limit > > > which we helped sponsor. > > > Not sure who the current maintainer is, but they piped up a while ago > > > and said they may get around to a release. > > > rdiff-backup still uses this very extensively, so the project needs to > > > exist > > I'm still around too and have all the admin level access to the project > on SF necessary to give people access permissions etc. I still also do > the periodic list cleanups. > > I am still interested in contributing to this project, but reality keeps > me occupied on other things. If there were other people willing to take > on revitalising this project I'd be happy to give people access etc. It seems that people in this maillist left for quite a while. But I did contact with Martin Pool, and found some useful info. Is there still anyone in charge of this project now? I have take a simple look of the source codes. APIs is quite simple and very useful. I'm really interesting in this lib. As I don't fully understand the whole codes, might be a little bit difficult for me to do something right now. I have been use code from source forge for a while. And i wish that I can do something about it. Maybe we can discuss about it. As I think I DO have a little spare time after July. > > > > dave > > > > > > -- > > > Regards, > > > > > > Dave Kempe > > > Solutions First > > > Phone: (02) 9923 2180 > > > Mobile: 0413 022 143 > > > Support requests: su...@so... > > > > > > ----- "Daniel.Li" <dan...@us...> wrote: > > > > > > > Dear List, > > > > > > > > I found that librsync is quite an old project. I wanna know, if > > > there > > > > is > > > > anyone home? > > > > > > > > :) Cause, I wanna do something about it. Thanks. > > > > -- > > > > Daniel -- Daniel |
From: Donovan B. <ab...@mi...> - 2009-05-08 12:40:10
|
On Tue, 2009-04-21 at 13:17 +0800, Daniel.Li wrote: > Thanks Dave. > > I'll study the code first and try to see what I can do with it. :) > > On Tue, 2009-04-21 at 14:38 +1000, Dave Kempe wrote: > > Nope, no one is home. The last patch was the fix the 4gb file limit > > which we helped sponsor. > > Not sure who the current maintainer is, but they piped up a while ago > > and said they may get around to a release. > > rdiff-backup still uses this very extensively, so the project needs to > > exist I'm still around too and have all the admin level access to the project on SF necessary to give people access permissions etc. I still also do the periodic list cleanups. I am still interested in contributing to this project, but reality keeps me occupied on other things. If there were other people willing to take on revitalising this project I'd be happy to give people access etc. > > dave > > > > -- > > Regards, > > > > Dave Kempe > > Solutions First > > Phone: (02) 9923 2180 > > Mobile: 0413 022 143 > > Support requests: su...@so... > > > > ----- "Daniel.Li" <dan...@us...> wrote: > > > > > Dear List, > > > > > > I found that librsync is quite an old project. I wanna know, if > > there > > > is > > > anyone home? > > > > > > :) Cause, I wanna do something about it. Thanks. > > > -- > > > Daniel -- Donovan Baarda <ab...@mi...> http://minkirri.apana.org.au/~abo/ |
From: Daniel.Li <dan...@us...> - 2009-04-21 05:17:56
|
Thanks Dave. I'll study the code first and try to see what I can do with it. :) On Tue, 2009-04-21 at 14:38 +1000, Dave Kempe wrote: > Nope, no one is home. The last patch was the fix the 4gb file limit > which we helped sponsor. > Not sure who the current maintainer is, but they piped up a while ago > and said they may get around to a release. > rdiff-backup still uses this very extensively, so the project needs to > exist > dave > > -- > Regards, > > Dave Kempe > Solutions First > Phone: (02) 9923 2180 > Mobile: 0413 022 143 > Support requests: su...@so... > > ----- "Daniel.Li" <dan...@us...> wrote: > > > Dear List, > > > > I found that librsync is quite an old project. I wanna know, if > there > > is > > anyone home? > > > > :) Cause, I wanna do something about it. Thanks. > > -- > > Daniel -- USI/SH RD Dept. Universal Scientific Industrial (Shanghai) Co., Ltd Fax: +86-21-58967931 Tel: +86-21-58966996 ext. 1400 42th building, 1387 Zhang Dong road, Pudong New Area, Shanghai, P.R. China 201203 |
From: Daniel.Li <dan...@us...> - 2009-04-21 02:41:23
|
Dear List, I found that librsync is quite an old project. I wanna know, if there is anyone home? :) Cause, I wanna do something about it. Thanks. -- Daniel |
From: Joachim H. <ach...@we...> - 2007-04-29 13:41:04
|
Hello, just wondering why this project is so dead. Great work has been done .. as it seems over years, to get a great algorithm into a library format and there were/are some ideas floating around related to this library. Still it is stuck at beta and doesn't appear to make the 1.0 release in near future. And using idle CPU power to accelerate network backup / data transfer should be an ever hot topic, at least where performance is bottlenecked by bandwidth. rsync is extremely popular at university and in the hpc sector, to synchronise fileservers, machines cross campus, cluster nodes from the master or to run disk backups. A portable library which exposes the rsync algorithm makes a lot of sense to me. From my perspective, librsync lacks a revision and an updated docu rather more than any additional features. Personally, I would like to use librsync multi-platform and "hacked" a version together which compiles a .dll under windows. The API does the trick for me, and I can connect network or file streams to the internal buffer structure. I don't need any fancy higher level stuff, which can be implemented in a different language, but I'd (selfishly) wish that the core functionality would be better maintained and documented. I hope this doesn't come accross as criticism, as I genuinely respect the work that has been done here. Joachim |
From: Donovan B. <ab...@mi...> - 2007-04-17 12:38:38
|
On Mon, 2007-04-16 at 13:29 +0200, Henrik Zagerholm wrote: > Hello Donovan, > > Sorry for pinging you offline but a critical error came up in my > project so I thought I could save some time contacting you directly. > > I'm working with a project using librsync in a *nix environment. I'm > using the 0.9.7 code as a base but will probably check out the latest > soon. > Any ideas on a release date for 0.9.8 yet? As soon as someone gets around to it... I'm pretty busy these days but it is hanging around on my todo list. > The problem I have is that now I need to run librsync on windows but > I couldn't get the compile working (using VS 2005). > I haven't looked into it that deeply yet because of time issues. > Fortunately I found your precompiled rsync 0.9.6 and its been working > as a charm on the winboxes I've tested. I didn't even realise I had one hanging around :-) > Now though I have had problems with big files and I wonder if you > have a newer precompiled version somewhere? > It would save me a lot of time right now. Hopefully I can get my own > librsync to compile on windows later on but till then I would really > appreciate if you had one laying around. =) The bad news is I nolonger have access to a win32 development environment. > Take care and thanks for all the good work you have put into this > project. I've actually been neglecting it pretty badly... I'm always keen to add more developers to this project so that there are more people to keep it kicking on... let me know if you want devel access to do things like release 0.9.8 :-) -- Donovan Baarda <ab...@mi...> http://minkirri.apana.org.au/~abo/ |
From: Harshal <vis...@sp...> - 2006-11-07 10:23:24
|
Hello everybody , I have used librsync 0.9.7 library with VC++. Now i have to develop an application in Managed VC++ .Net. Will i be able to use the same library for Managed VC++ .Net? Or whether I have to get some other version for Managed VC++.Net.? Waiting for your reply. Thanking you Harshal |
From: Corey P. <cp...@gm...> - 2006-11-07 06:33:46
|
Greetings librsync developer(s)... I'm an rdiff-backup user who has been running into the 4GB+ file problem which I understand has been fixed in librsync cvs. I'm wondering if there's any chance of a release being made or is librsync (and thus, rdiff-backup as well) a completely dead project? Thanks, Corey |
From: Donovan B. <ab...@mi...> - 2006-08-27 11:31:13
|
[adding Cc librsync-devel] Martin Pool wrote: > On 24 Aug 2006, roland <de...@we...> wrote: >> hello librsync authors! >> >> I already tried to contact librsync team some time ago, but maybe this was >> adressed to the wrong people. >> >> the last official librsync release is some time ago: >> >> 0.9.7 [Notes] (2004-10-10 03:20) librsync-0.9.7.tar.gz >> 0.9.6 [Notes] (2003-08-07 07:00) librsync-0.9.6.tar.gz >> 0.9.5 [Notes] (2001-09-13 00:00) librsync-0.9.5.tar.gz >> >> what about releasing a 0.9.8 ? >> >> I think the current cvs contains a very important patch, so that >> librsync/rdiff will work without problems with large files (see below). > > Donovan (abo) was last maintainer for it. If he's not reachable then I > could make a release. I am reachable, just very short of time and hence slow to respond... I still do minor things when prompted like list admin, but I probably don't have time to do a release right now... so if someone else could do it that would be great. Have a look at the end of README.CVS for a rough checklist of things to do for a release. On this particular issue, I've not been keeping up much, but I vaugely recall that there was some ambiguity if the problem was fixed after the patch went in (see bug #1110812). However, the patch #1439412 definitely fixed one problem and is worth a release for. Boy, SF is pretty flakey ATM... it is giving me intermittent 500's. I'll have a bit of a poke around at the source and see if there are any quick things I can do to prepare for a release... -- Donovan Baarda <ab...@mi...> |
From: Martin P. <mb...@ca...> - 2006-06-14 20:08:45
|
On 15/06/2006, at 6:01 AM, Ranga Nathan wrote: > I am installing rdiff-backup which needs librsync-devel-0.9.7. > Can someone point me to a download link? There are some links that > seem > to be for x86 but I need to build this for s390 (IBM mainframe). You should be able to get it from librsync.sf.net download link. -- Martin |
From: Ranga N. <kai...@gm...> - 2006-06-14 20:01:53
|
I am installing rdiff-backup which needs librsync-devel-0.9.7. Can someone point me to a download link? There are some links that seem to be for x86 but I need to build this for s390 (IBM mainframe). |
From: roland <de...@we...> - 2006-05-05 17:17:49
|
Hello ! As a user of rdiff-backup i had severe problems with files larger than 4gb. After seraching for the cause of the bug i found this Bug-ID in librsync and tried to compile it from cvs version. seems that the problem is gone now - fine :) but -I wonder why there wasn`t a change in release number of librsync/rdiff !? is this bugfix not important enough (i think it`s major bug) - or does just need some time to pass by to wait for positive/negative feedback ? any plans for making a new release so we can expect this bug (and probably others) being fixed in all sort of distro's packages ? regards roland |
From: Ben E. <be...@em...> - 2006-04-30 23:55:20
|
>>>>> Sekar Vembu <se...@ve...> >>>>> wrote the following on Mon, 20 Mar 2006 19:18:17 +0530 > Sorry about not using the SF patch tracker. We will learn the right way=20 > to send patches in the future. Hopefully these fixes are useful and you=20 > can incorporate it with the right approach in the librsync source code. Yes, I for one am ecstatic that someone seems to have finally tracked down the 4Gb+ bug. People post about this from time to time on the rdiff-backup list and it's not clear if it's librsync or not, and the probably only occurs sometimes. So, if you fixed it, great work! :-) --=20 Ben Escoto |
From: Donovan B. <ab...@mi...> - 2006-03-20 13:59:31
|
On Mon, 2006-03-20 at 19:18 +0530, Sekar Vembu wrote: > Sorry about not using the SF patch tracker. We will learn the right way > to send patches in the future. Hopefully these fixes are useful and you > can incorporate it with the right approach in the librsync source code. Thanks... also, it is worth subscribing to the librsync-dev list on SF... it means I don't have to keep approving your non-subscriber posts. These fixes are definitely useful and will go in... the only thing yet to be determined is how and when :-) > Thanks > Sekar > > Donovan Baarda wrote: > > >On Mon, 2006-03-20 at 18:18 +0530, Sekar Vembu wrote: > > > > > >>Hi, > >>Subsequent to my original email, I think we have fixed the large file > >>problem in Windows too. We have made minor modifications to three files. > >>We have tested this and it seems to work for us. I am attaching the > >>three files with this email. > >>1. buf.c > >>2. librsync.h > >>3.PcBuild\librsync-config.h > >> > >>The following are the cvs-diff for those three files. Hope some expert > >>will review this and check this in to the librsync CVS. If there is a > >>problem with these changes please let me know. > >> > >> > > > >Please submit patches at the SF patch tracker... > > > >Also, looking at this, I have a feeling this is compiler dependant, > >rather than just WIN32 dependent. I suspect this stuff should be handled > >by configure, rather than peppering the code with more #if WIN32 stuff. > >Note that PCBuild/librsync-config.h should be auto-generated by running > >configure with a MSC system. > > > >In any case, thanks for this... if no one else gets around to it before > >me, I'll look into it and see what the best approach for this is... > > > > > > -- Donovan Baarda <ab...@mi...> http://minkirri.apana.org.au/~abo/ |
From: Sekar V. <se...@ve...> - 2006-03-20 13:50:48
|
Sorry about not using the SF patch tracker. We will learn the right way to send patches in the future. Hopefully these fixes are useful and you can incorporate it with the right approach in the librsync source code. Thanks Sekar Donovan Baarda wrote: >On Mon, 2006-03-20 at 18:18 +0530, Sekar Vembu wrote: > > >>Hi, >>Subsequent to my original email, I think we have fixed the large file >>problem in Windows too. We have made minor modifications to three files. >>We have tested this and it seems to work for us. I am attaching the >>three files with this email. >>1. buf.c >>2. librsync.h >>3.PcBuild\librsync-config.h >> >>The following are the cvs-diff for those three files. Hope some expert >>will review this and check this in to the librsync CVS. If there is a >>problem with these changes please let me know. >> >> > >Please submit patches at the SF patch tracker... > >Also, looking at this, I have a feeling this is compiler dependant, >rather than just WIN32 dependent. I suspect this stuff should be handled >by configure, rather than peppering the code with more #if WIN32 stuff. >Note that PCBuild/librsync-config.h should be auto-generated by running >configure with a MSC system. > >In any case, thanks for this... if no one else gets around to it before >me, I'll look into it and see what the best approach for this is... > > > |
From: Donovan B. <ab...@mi...> - 2006-03-20 13:43:29
|
On Mon, 2006-03-20 at 18:18 +0530, Sekar Vembu wrote: > Hi, > Subsequent to my original email, I think we have fixed the large file > problem in Windows too. We have made minor modifications to three files. > We have tested this and it seems to work for us. I am attaching the > three files with this email. > 1. buf.c > 2. librsync.h > 3.PcBuild\librsync-config.h > > The following are the cvs-diff for those three files. Hope some expert > will review this and check this in to the librsync CVS. If there is a > problem with these changes please let me know. Please submit patches at the SF patch tracker... Also, looking at this, I have a feeling this is compiler dependant, rather than just WIN32 dependent. I suspect this stuff should be handled by configure, rather than peppering the code with more #if WIN32 stuff. Note that PCBuild/librsync-config.h should be auto-generated by running configure with a MSC system. In any case, thanks for this... if no one else gets around to it before me, I'll look into it and see what the best approach for this is... -- Donovan Baarda <ab...@mi...> http://minkirri.apana.org.au/~abo/ |