On Fri, Jun 04, 2010 at 02:37:01PM -0700, Christopher Wingert wrote:
>On Fri, Jun 04, 2010 at 03:16:43PM -0600, Eric Blake wrote:
>>On 06/04/2010 03:14 PM, Christopher Wingert wrote:
>>>Agreed, I would like to make a global change, however, unless I can
>>>talk to the current maintainer of the fha
He is? Holy crap, he is more helpful with his sarcasm and doubt than
anything else. However, it does explains his tone, given that I am
picking on his code.
I see your reference to an acronym regarding top posting, but not a
policy. In fact your reference is specifically listed under another
ob
On 06/04/2010 03:14 PM, Christopher Wingert wrote:
> Agreed, I would like to make a global change, however, unless I can talk
> to the current maintainer of the fhandler* functions, it seems illogical
> for me to change them (as I have about a week of cygwin dll experience).
You ARE talking to the
See further down the thread, the right solution is to impact ALL cygwin
executables, but I don't have the experience in the dll to make those
changes.
> On 6/4/2010 2:20 PM, Christopher Faylor wrote:
>>> "But providing a variant of stat() along the lines of what you propose
>>> above is not pract
I actually wrote my own rsync in AutoIt, but it is also limited.
However, I thought it would a nice addition to speed up Cygwin. As I have
been using it for about 10 years and made my transition from Linux to
Windows so pleasant.
> On 4 June 2010 19:50, Eliot Moss wrote:
>> I don't think there'
Agreed, I would like to make a global change, however, unless I can talk
to the current maintainer of the fhandler* functions, it seems illogical
for me to change them (as I have about a week of cygwin dll experience).
Also my interest in performance is limited to a very certain subset of
executab
On 4 June 2010 19:50, Eliot Moss wrote:
> I don't think there's an objection here to
> patching *rsync* specially in the cygwin
> environment -- that would be between you
> and the rsync port maintainer. The issue
> is whether or not to make a more general
> change to cygwin itself, and cgf is just
I don't think there's an objection here to
patching *rsync* specially in the cygwin
environment -- that would be between you
and the rsync port maintainer. The issue
is whether or not to make a more general
change to cygwin itself, and cgf is just
saying that that's hard to do.
Conceivably we cou
On 6/4/2010 2:20 PM, Christopher Faylor wrote:
"But providing a variant of stat() along the lines of what you propose
above is not practical for all the reasons already stated."
This is not something that I said. That was actually Larry Hall.
Heh. Who needs him anyway!
Just to clarify, this
On Fri, Jun 04, 2010 at 10:33:47AM -0700, Christopher Wingert wrote:
>Eric Blake wrote:
>> [quit top-posting]
>
>Now you are my mom too?
"too?" I don't recall any other responses from Eric to you.
>> That's where you're wrong. Any patch you write that is technically
>> sound and shows a measura
On Fri, Jun 04, 2010 at 10:07:58AM -0700, Christopher Wingert wrote:
>Again, not production, this was to highlight a point and to enhance (I
>would assume) the most common use case (file to file rsync).
>
>Plenty of solutions for a good patch, complete the Windows version of
>stat() or call the Cyg
> [quit top-posting]
Now you are my mom too?
> That's where you're wrong. Any patch you write that is technically
> sound and shows a measurable improvement will most likely be accepted.
Then you shouldn't have Cygwin's front line technical spokesman saying
things such as:
"If there was a way
[quit top-posting]
On 06/04/2010 11:07 AM, Christopher Wingert wrote:
> Again, not production, this was to highlight a point and to enhance (I
> would assume) the most common use case (file to file rsync).
>
> Plenty of solutions for a good patch, complete the Windows version of
> stat() or call
Again, not production, this was to highlight a point and to enhance (I
would assume) the most common use case (file to file rsync).
Plenty of solutions for a good patch, complete the Windows version of
stat() or call the Cygwin version if the Window's version fails.
Since I don't have any confide
- Original Message -
From: "Adi B Treiner"
To: Cygwin
Cc: Pierre.Humblet
Sent: Friday, June 04, 2010 10:43
Hello Pierre,
thanks fort the response.
> Did you upgrade from 1.5 to 1.7.5 or did you go through some 1.7.X?
I think I upgraded from 1.5 to 1.7.5 directly.
> This problem may
On 6/4/2010 12:37 PM, Christopher Wingert wrote:
So here is an example of a performance gain by not using cygwin stat(). I
did this patch in about an hour (with the help of some git code), so I
wouldn't recommend it for any production use.
On a dry run rsync from my local drive to my NAS (105GB
So here is an example of a performance gain by not using cygwin stat(). I
did this patch in about an hour (with the help of some git code), so I
wouldn't recommend it for any production use.
On a dry run rsync from my local drive to my NAS (105GB, 34k files, 4k
directories). The current release
> Please update the unison* packages as follows:
Sorry, wrong list. Please ignore.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-
Please update the unison* packages as follows:
- Add the new unison2.40 package (new beta release)
- Update unison2.27, unison2.32
Thanks,
Andrew.
cd release/unison
B='http://home.comcast.net/~andrex2/cygwin/unison'
wget -x -nH --cut-dirs=3 \
${B}/unison2.40/setup.hint \
${B}/unison2.40/unison
Hello Pierre,
thanks fort the response.
> Did you upgrade from 1.5 to 1.7.5 or did you go through some 1.7.X?
I think I upgraded from 1.5 to 1.7.5 directly.
> This problem may be due to the way the groups are computed in Cygwin
> 1.7 but there must be something special about your install, oth
On 6/4/2010 7:57 AM, prakash babu wrote:
Since Cygwin 1.7 does not support MS-DOS style paths for chmod , I installed
cygwin 1.5 using legacy-setup.exe
The flaw in this logic is the assumption that Cygwin 1.5 supports MS-DOS
style paths 'for chmod'. It may handle things a little differently bu
On 2 June 2010 15:53, Corinna Vinschen wrote:
> On Jun 2 15:56, Corinna Vinschen wrote:
>> On Jun 2 13:55, Christian Franke wrote:
>> > Andy Koppe wrote:
>> > > On Cygwin 1.7:
>> > > $ ls -l //foo/bar
>> > > -rw-r--r-- 1 andy Administrators 0 Dec 1 2006 //foo/bar
>> > >
>> > > Server 'foo' does
> From: Eric Blake
> Sent: Thursday, June 03, 2010 16:20
> To: cygwin@cygwin.com
> Subject: Re: C: vs /cygdrive/c and git
>
...
>
> If drive letters work, great for you. But if they don't, I am not going
> to spend any time beating up the source code to make them work. They
> are intentionally
--- On Fri, 6/4/10, Larry Hall (Cygwin)
wrote:
> 1.5.25 is no longer supported. The current version is
> 1.7.5.
I have downloaded the setup and will install this weekend.
Thanks.
sj
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/f
Since Cygwin 1.7 does not support MS-DOS style paths for chmod , I installed
cygwin 1.5 using legacy-setup.exe
The installation went fine but the C:\\cygwin\\bin has only two binaryies
ash.exe and cygrunsrv.exe. Also the Cygwin.bat exits immediately after invoking
Is there any document availabl
On 6/4/2010 2:44 AM, Nasser M. Abbasi wrote:
On 6/4/2010 1:36 AM, Corinna Vinschen wrote:
Error: Cannot read 'img2.png': No such file or directory
Converting image #1
0 [main] perl 3400 C:\cygwin\bin\perl.exe: *** fatal error -
Internal error: TP_NUM_W_BUFS too small."
This looks l
On 6/4/2010 1:36 AM, Corinna Vinschen wrote:
Error: Cannot read 'img2.png': No such file or directory
Converting image #1
0 [main] perl 3400 C:\cygwin\bin\perl.exe: *** fatal error -
Internal error: TP_NUM_W_BUFS too small."
This looks like an internal error in Cygwin which runs out
> From: Oleksandr Gavenko
> Date: Thu, 03 Jun 2010 23:33:44 +0300
> Cc: cygwin@cygwin.com
>
> %* in .bat file not proper work - it strip all chars after
> first new line occurrence.
>
> I think in Windows there are no anything scriptable with
> "$*" like in POSIX sh.
Yes, there is: it's %*. Th
On Jun 3 12:02, Nasser M. Abbasi wrote:
> On 6/3/2010 12:43 AM, n...@12000.org wrote:
> >Hello,
> >
> >SUMMARY:
> >
> >I installed cygwin 1.7.5 on windows 7 (64 bit OS), and when I run some
> >command which uses perl, I get the following error:
> >
> >0 [main] perl 2528 C:\cygwin\bin\perl.exe: ***
29 matches
Mail list logo
