Hi,
I am interested in becoming a maintainer for a new package mlcscope.
I have attached the setup.hint
The original distribution of mlcscope can be found at
http://www.bell-labs.com/project/wwexptools/packages.html as part of the
cscope distribution.
I have placed a source and binary set
Dave Diane wrote:
I have placed a source and binary set of archives for the cygwin package
at http://www.lowtechnet.com/cscope
I have not created a cygwin package before, so if I screwup in this
process, I apologise in advance.
Before sending email to cygwin-announce I have a few
On Sat, 17 Jun 2006, Christopher Faylor wrote:
On Sat, Jun 17, 2006 at 03:13:45PM -0400, Igor Peshansky wrote:
On Fri, 16 Jun 2006, Christopher Faylor wrote:
X maintainer?
Oh, a thinly veiled hint... :-)
It's not a hint. We don't have an X maintainer.
I thought Yaakov was working on
Igor Peshansky wrote:
I thought Yaakov was working on becoming one eventually... This was
mostly a hint to him that he may want to take over the other duties of the
X maintainer... But then, I'm not even sure he's subscribed to this list
yet, so the hint may have been premature.
I am, but
CVSROOT:/cvs/src
Module name:src
Changes by: [EMAIL PROTECTED] 2006-06-18 08:16:55
Modified files:
winsup/mingw : ChangeLog
winsup/mingw/include/sys: time.h
winsup/mingw/mingwex: Makefile.in
Added files:
winsup/mingw/mingwex:
CVSROOT:/cvs/src
Module name:src
Changes by: [EMAIL PROTECTED] 2006-06-18 08:43:34
Modified files:
winsup/mingw : ChangeLog
winsup/mingw/mingwex: dirent.c
Log message:
* mingwex/dirent.c (_tGetFileAttributes): New helper function.
CVSROOT:/cvs/src
Module name:src
Changes by: [EMAIL PROTECTED] 2006-06-18 13:35:01
Modified files:
winsup/mingw : ChangeLog configure
Log message:
2006-06-18 Chris Sutcliffe [EMAIL PROTECTED]
* configure: add srcdir as a possible
CVSROOT:/cvs/src
Module name:src
Changes by: [EMAIL PROTECTED] 2006-06-18 23:06:56
Modified files:
winsup/mingw : ChangeLog configure.in configure
Log message:
* configure.in (AC_CONFIG_AUX_DIR): Remove.
* configure: Regenerate.
Patches:
Hi,
Tue, 16 May 2006 I wrote:
Would someone please tell me what file(s) I would have to take with
me (eg. on a disk) to someone else's machine, both running windows XP,
whereby I could get setup to download the same cygwin components that
are on my machine?
Wed, 17 May 2006 I wrote:
I
Just sending the OPs reply so that it is in the mailing list archive.
Mark Hessling wrote:
Mark Hessling wrote:
Actually, what you describe is clear enough, but since CRLF handling
isn't done by the Linux version of sed either, you would have the same
problem on Linux. The question here is
On Sun, 18 Jun 2006, Jim Easton wrote:
Hi,
Tue, 16 May 2006 I wrote:
Would someone please tell me what file(s) I would have to take with
me (eg. on a disk) to someone else's machine, both running windows XP,
whereby I could get setup to download the same cygwin components that
are on
On Sun, 18 Jun 2006, Igor Peshansky wrote:
On Sun, 18 Jun 2006, Jim Easton wrote:
Hi,
Tue, 16 May 2006 I wrote:
Would someone please tell me what file(s) I would have to take with
me (eg. on a disk) to someone else's machine, both running windows XP,
whereby I could get setup to
--On 16 June 2006 16:49 -0400 Hochstedler, Ben (GE Healthcare) wrote:
fork() can fail when the system runs out of non-interactive heap space
(because there's not enough heap memory to allocate to the launched
process).
If we, as end-users, suffer from fork() failing for the above reason,
Brian Dessent wrote:
Science Guy wrote:
This problem has been noted before by someone else,
http://www.mail-archive.com/cygwin@cygwin.com/msg37532.html
but I followed the threads and can find no resolution.
When I fire-up a cygwin bash window, everything is fine for a few minutes.
Corinna Vinschen wrote:
I have updated the version of vim on cygwin.com to 7.0.017-1.
This is the long awaited vim 7.0, latest patchlevel 17. Cygwin Vim
still builds from the vanilla sources.
---
Vim 7 seems to still have a few kinks to work out and doesn't
seem nearly as stable as
Linda Walsh wrote:
I didn't see Science Guy mention procexp? Um, hey, S.G.,
are you using Process Explorer?
There are probably other programs that use the same technique and cause
the same effect, like windows update.
I remember the ProcExp bug, but it only happened when I tried to
Linda Walsh wrote:
[snip]
Vim 7 seems to still have a few kinks to work out and doesn't
seem nearly as stable as vim64. Since vim7 is already out as vim,
maybe vim6.4 could be made available as a separete vim6 or vim64
package for those not wanting to be on the bleeding edge?
It is
On Sun, Jun 18, 2006 at 03:18:13PM -0700, Brian Dessent wrote:
Linda Walsh wrote:
I didn't see Science Guy mention procexp? Um, hey, S.G., are you using
Process Explorer?
There are probably other programs that use the same technique and cause
the same effect, like windows update.
I remember the
18 matches
Mail list logo
