On Thu, Mar 03, 2011 at 02:53:13PM +0200, Oleg Marchuk wrote:
>I fixed error with downgrade cygwin package from 1.7.8-1 to 1.7.7-1
Or, you could, ...you know... please test the latest developer snapshot
cgf
--
Problem reports: http://cygwin.com/problems.html
FAQ: http
I fixed error with downgrade cygwin package from 1.7.8-1 to 1.7.7-1
On Thu, Mar 3, 2011 at 2:22 PM, Oleg Marchuk wrote:
> I have got error similar to one described in
> http://www.mail-archive.com/cygwin at cygwin.com/msg114840.html
>
> Cygwin works fine until I install screens, try using git in
I have got error similar to one described in
http://www.mail-archive.com/cygwin at cygwin.com/msg114840.html
Cygwin works fine until I install screens, try using git in screens,
get error related to git repository name in prompt and then uninstall
screens.
In screens:
sh: __git_ps1: command not
On 2/28/2011 11:06 PM, Christopher Faylor wrote:
> On Fri, Feb 25, 2011 at 04:09:44PM -0800, David Rothenberger wrote:
>> On 2/25/2011 3:24 PM, David Rothenberger wrote:
>>> I realize this report won't be terribly useful, but I did encounter
>>> a problem with the latest snapshot. I have a local gi
On Fri, Feb 25, 2011 at 04:09:44PM -0800, David Rothenberger wrote:
>On 2/25/2011 3:24 PM, David Rothenberger wrote:
>> I realize this report won't be terribly useful, but I did encounter
>> a problem with the latest snapshot. I have a local git
>> repository. With the snapshot, "git log" produces:
On 2/27/2011 2:20 AM, Corinna Vinschen wrote:
> On Feb 26 11:35, Corinna Vinschen wrote:
>> On Feb 25 16:09, David Rothenberger wrote:
>>> I was able to reproduce this using a clone of the git repository itself:
>>>
>>> % uname -a
>>> CYGWIN_NT-5.1 tela 1.7.8s(0.236/5/3) 20110221 20:36:00 i686 Cygw
Corinna Vinschen wrote:
If it works for you, and still works for others,
It works for me (WinXP SP3), I think:
$ uname -a
CYGWIN_NT-5.1 mypc 1.7.8s(0.236/5/3) 20110227 02:35:16 i686 Cygwin
$ git clone git://github.com/git/git.git
Cloning into git...
remote: Counting objects: 134777, done.
rem
On Feb 26 11:35, Corinna Vinschen wrote:
> On Feb 25 16:09, David Rothenberger wrote:
> > I was able to reproduce this using a clone of the git repository itself:
> >
> > % uname -a
> > CYGWIN_NT-5.1 tela 1.7.8s(0.236/5/3) 20110221 20:36:00 i686 Cygwin
> > % git clone git://github.com/git/git.git
On Sat, Feb 26, 2011 at 4:03 AM, Thomas Wolff wrote:
> No, what used to work (and didn't work in cygwin for a while) is that the
> current directory of some process is removed, not mentioning how it could be
> removed.
Sure, this is pre-requisite of rmdir("."). I was specifically talking about
rm
On Feb 25 16:09, David Rothenberger wrote:
> I was able to reproduce this using a clone of the git repository itself:
>
> % uname -a
> CYGWIN_NT-5.1 tela 1.7.8s(0.236/5/3) 20110221 20:36:00 i686 Cygwin
> % git clone git://github.com/git/git.git
> Cloning into git...
> remote: Counting objects: 134
On Sat, Feb 26, 2011 at 1:09 AM, David Rothenberger wrote:
> On 2/25/2011 3:24 PM, David Rothenberger wrote:
>> I realize this report won't be terribly useful, but I did encounter
>> a problem with the latest snapshot. I have a local git
>> repository. With the snapshot, "git log" produces:
>>
>>
Am 26.02.2011 01:24, schrieb Vorfeed Canal:
On Mon, Feb 21, 2011 at 6:20 PM, Thomas Wolff wrote:
And this is not an artificial limitation but there is no way that this
could conceivably work.
What do you mean "there is no way that this could conceivably work"?
It worked in Linux till it was e
On 02/25/2011 05:24 PM, Vorfeed Canal wrote:
> On Mon, Feb 21, 2011 at 6:20 PM, Thomas Wolff wrote:
>> And this is not an artificial limitation but there is no way that this
>> could conceivably work.
>
> What do you mean "there is no way that this could conceivably work"?
>
> It worked in Linux
On Mon, Feb 21, 2011 at 6:20 PM, Thomas Wolff wrote:
> And this is not an artificial limitation but there is no way that this
> could conceivably work.
What do you mean "there is no way that this could conceivably work"?
It worked in Linux till it was explicitly forbidden...
See here, for examp
On 2/25/2011 3:24 PM, David Rothenberger wrote:
> I realize this report won't be terribly useful, but I did encounter
> a problem with the latest snapshot. I have a local git
> repository. With the snapshot, "git log" produces:
>
> 0 [main] git 4944 C:\cygwin\bin\git.exe: *** fatal error - c
I realize this report won't be terribly useful, but I did encounter
a problem with the latest snapshot. I have a local git
repository. With the snapshot, "git log" produces:
0 [main] git 4944 C:\cygwin\bin\git.exe: *** fatal error - could not load
C:\WINDOWS\system32\winmm.dll, Win32 error
On various days, various members of the Cygwin community wrote:
> [...snapshot testing...]
Wow, that's all pretty good news. Thanks to all of you for testing
the snapshots. Stay tuned for the release.
Thanks again,
Corinna
--
Corinna Vinschen Please, send mails regarding Cyg
Yes, good progress. A lot of those x64 Win7 issues don't appear
anymore for me and I didn't had now for some time no more forking
issues.
Thanks,
Kai
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/do
>> Please test latest developer snapshot
Lots of perl builds and smokes passed with no new errors.
--
Reini
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cy
> Date: Thu, 24 Feb 2011 16:16:11 +0100
> From: corinna
> Subject: Re: Please test latest developer snapshot
>
> On Feb 24 09:56, Chris Sutcliffe wrote:
> > On 17 February 2011 07:04, Corinna Vinschen wrote:
> > > Apart fr
On Feb 24 09:56, Chris Sutcliffe wrote:
> On 17 February 2011 07:04, Corinna Vinschen wrote:
> > Apart from your testing and our fixing of obvious bugs, the other item
> > holding up the release of Cygwin 1.7.8 is the imminent release of
> > Service Pack 1 for Windows 7. It seems unwise to release
On 17 February 2011 07:04, Corinna Vinschen wrote:
> Apart from your testing and our fixing of obvious bugs, the other item
> holding up the release of Cygwin 1.7.8 is the imminent release of
> Service Pack 1 for Windows 7. It seems unwise to release a new Cygwin
> package just minutes before a Se
Am 21.02.2011 15:16, schrieb Eric Blake:
> On 02/19/2011 11:29 AM, Warren Young wrote:
>
>> On 2/17/2011 5:04 AM, Corinna Vinschen wrote:
>>
>>> - Reintroduce the ability to delete an empty directory which is the
>>>current working directory of the same or another Cygwin process.
>>>
On 02/19/2011 11:29 AM, Warren Young wrote:
> On 2/17/2011 5:04 AM, Corinna Vinschen wrote:
>> Hi crowd,
>
> rabble? angry mob?
>
>> - Reintroduce the ability to delete an empty directory which is the
>>current working directory of the same or another Cygwin process.
>
> I don't see that. T
On Feb 19 13:34, Warren Young wrote:
> On 2/19/2011 11:35 AM, Warren Young wrote:
> >On 2/19/2011 11:29 AM, Warren Young wrote:
> >>$ rmdir .
> >>rmdir: failed to remove `.': Invalid argument
> >
> >Nevermind. It doesn't work on Linux, either. I guess /bin/rmdir has code
> >in it to check for that,
On 2/19/2011 11:35 AM, Warren Young wrote:
On 2/19/2011 11:29 AM, Warren Young wrote:
$ rmdir .
rmdir: failed to remove `.': Invalid argument
Nevermind. It doesn't work on Linux, either. I guess /bin/rmdir has code
in it to check for that, which rmdir(2) does not.
Better test, which does wor
On 2/19/2011 11:29 AM, Warren Young wrote:
$ rmdir .
rmdir: failed to remove `.': Invalid argument
Nevermind. It doesn't work on Linux, either. I guess /bin/rmdir has
code in it to check for that, which rmdir(2) does not.
--
Problem reports: http://cygwin.com/problems.html
FAQ:
On 2/17/2011 5:04 AM, Corinna Vinschen wrote:
Hi crowd,
rabble? angry mob?
- Reintroduce the ability to delete an empty directory which is the
current working directory of the same or another Cygwin process.
I don't see that. Testcase:
$ mkdir foo
$ cd foo
$ rmd
I have tested the bugs I reported about Varnish Cache program and It
works fine with last snapshot:
- Make sure that the random number generator is seeded on a
per-thread basis.
- Fix bind(2) behaviour related to SO_REUSEADDR.
and they works ok. New madvise call also works ok.
--
Problem
Corinna Vinschen wrote:
And, btw., if you find that something suddenly starts working better
using the snapshot, I'd be happy to hear this. Good news help to
keep up the spirit.
It seems that, with this snapshot, the slowdown I flagged after the
release of 1.7.6[*], reverted (almost). Now the
On Fri, Feb 18, 2011 at 1:35 PM, Corinna Vinschen wrote:
> On Feb 17 19:14, marco atzeri wrote:
>> On Thu, Feb 17, 2011 at 1:04 PM, Corinna Vinschen wrote:
>> > Hi crowd,
>> >
>> >
>> > After the last round of patches we're now heading towards the
>> > 1.7.8 release. Therefore I'd like to ask yo
On Feb 17 19:14, marco atzeri wrote:
> On Thu, Feb 17, 2011 at 1:04 PM, Corinna Vinschen wrote:
> > Hi crowd,
> >
> >
> > After the last round of patches we're now heading towards the
> > 1.7.8 release. Therefore I'd like to ask you to give the latest
> > developer snapshot from http://cygwin.com
On Thu, 2011-02-17 at 13:04 +0100, Corinna Vinschen wrote:
> And, btw., if you find that something suddenly starts working better
> using the snapshot, I'd be happy to hear this. Good news help to
> keep up the spirit.
I had also experienced problems on Win7 x64 after last week's Windows
update,
Corinna Vinschen cygwin.com> writes:
>
> And, btw., if you find that something suddenly starts working better
> using the snapshot, I'd be happy to hear this. Good news help to
> keep up the spirit.
>
The last snapshot I tested was 20110207, and with that one I still was unable to
start X, as
On Thu, Feb 17, 2011 at 1:04 PM, Corinna Vinschen wrote:
> Hi crowd,
>
>
> After the last round of patches we're now heading towards the
> 1.7.8 release. Therefore I'd like to ask you to give the latest
> developer snapshot from http://cygwin.com/snapshots/ a try.
Corinna,
could you check ?
$
On 2/17/2011 7:04 AM, Corinna Vinschen wrote:
[...]
And, btw., if you find that something suddenly starts working better
using the snapshot, I'd be happy to hear this. Good news help to
keep up the spirit.
emacs users should find that the long-standing timezone problem (see
/usr/share/doc/Cyg
36 matches
Mail list logo
