From: "Russ Cox" <rsc@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lucio-
Date: Wed, 9 Jan 2002 00:08:04 -0500 [thread overview]
Message-ID: <20020109050805.9394F19A70@mail.cse.psu.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1301 bytes --]
> No offense meant, but doesn't this show precisely what CVS's strength
> is? Had you recorded the fix, we wouldn't be still looking for it :-)
It shows that I should keep better
records of what I do each day.
Even if I had the CVS source under
CVS, I probably would have thrown out
the repository when I ported the new one.
Further, I'm not sure whether the bug was
in CVS or in APE.
If I remembered what was broken,
I could run history to find it.
Case in point: I just found it, by
poking around for files in /sys/src/ape
modified about the same date as when I
ported the new CVS (which I remember being
near when I found the bug).
CVS wouldn't have helped any more than the
dump here.
The bug is in /sys/src/ape/lib/ap/plan9/getcwd.c.
Replace the entire file with:
#include "lib.h"
#include <stddef.h>
#include <stdlib.h>
#include <unistd.h>
#include <errno.h>
#include <string.h>
#include <stdio.h>
#include "sys9.h"
#include "dir.h"
char*
getcwd(char *buf, size_t len)
{
int fd;
fd = _OPEN(".", OREAD);
if(fd < 0) {
errno = EACCES;
return 0;
}
if(_FD2PATH(fd, buf, len) < 0) {
errno = EIO;
_CLOSE(fd);
return 0;
}
_CLOSE(fd);
return buf;
}
Exercise to the reader: find the fd leak in the
original.
Russ
[-- Attachment #2: Type: message/rfc822, Size: 2436 bytes --]
From: Lucio De Re <lucio@proxima.alt.za>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] lucio-
Date: Wed, 9 Jan 2002 06:52:59 +0200
Message-ID: <20020109065259.G12098@cackle.proxima.alt.za>
On Tue, Jan 08, 2002 at 10:06:45PM -0500, Russ Cox wrote:
>
> For the list, I've fixed this bug before.
> I remember it being a neat bug, but I don't
> remember what it was. Once Lucio and I figure
> it out again, one of us will post what the
> problem was. Perhaps it was cvs, perhaps APE,
> perhaps some weird interaction between the
> two. I've been trying to remember all day.
>
No offense meant, but doesn't this show precisely what CVS's strength
is? Had you recorded the fix, we wouldn't be still looking for it :-)
But I agree wholeheartedly that CVS is only a partial solution and
that the needs it attempts to address vary widely. I'm tempted to
create a mailing list specially to discuss a CVS-like development
that merges the Plan 9 backup technology into it. Any takers?
++L
next reply other threads:[~2002-01-09 5:08 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-09 5:08 Russ Cox [this message]
2002-01-09 5:32 ` Lucio De Re
2002-01-09 6:01 ` Lucio De Re
2002-01-10 10:37 ` Bruce Janson
2002-01-10 12:07 ` Source version control (Was: [9fans] lucio-) Lucio De Re
2002-03-04 21:14 ` [9fans] lucio- Richard Uhtenwoldt
-- strict thread matches above, loose matches on Subject: below --
2002-03-05 1:42 Russ Cox
2002-03-05 0:10 geoff
2002-03-05 17:07 ` Dan Cross
2002-03-11 10:05 ` Luis Fernandes
2002-01-10 15:31 rob pike
2002-01-10 11:07 forsyth
2002-01-10 1:36 okamoto
2002-01-10 13:52 ` Boyd Roberts
2002-01-09 7:06 okamoto
2002-01-09 5:41 geoff
2002-01-09 3:06 Russ Cox
2002-01-09 4:49 ` Lucio De Re
2002-01-09 4:52 ` Lucio De Re
2002-01-09 10:58 ` Boyd Roberts
2002-01-09 16:01 ` Aharon Robbins
2002-01-09 1:04 okamoto
2002-01-08 18:01 Russ Cox
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020109050805.9394F19A70@mail.cse.psu.edu \
--to=rsc@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).