Julian Elischer wrote:
> I'd prefer to be working on a branch of CVS if it weren't for the people
> that would scream whenever I moved my merged tag up.
> (eek eek cvsup bloat).
> That way i would have a dozen people helping me but with my code in P4 I
> have me and occasionally Peter.
Everybody who can commit to cvs on freefall also has p4 access. The set of
people who can help is exactly the same. In fact, we even have a couple of
non-comitters with access. As I posted before, the instructions are in
http://people.freebsd.org/~peter/p4cookbook.txt, and the 'p4newuser'
command on freefall is what is run to activate it. If we want a majordomo
[EMAIL PROTECTED] mailing list (or something like that, as an analog to
[EMAIL PROTECTED]), I can have that set up as well.
> P4 is ok but it's strangling me because people have to get teh source to
> work on it and it's just a bit too hard to do so. And when they have it
> they can't just use CVS to generate diffs to send back etc.
Yes, they can. cvsup10 carries a change-by-change copy of your work. They
can do exactly what you said above.. ie: anybody can cvsup, and use cvs to
send diffs to you etc.
As I previously mailed, a sample supfile might look like this:
*default base=/tmp/cvs # change this
*default prefix=/tmp/cvs # change this
*default delete use-rel-suffix
peter@thunder[11:58pm]/tmp/cvs/projects/kse/sys/sys-126> rlog proc.h,v | more
RCS file: proc.h,v
Working file: proc.h
date: 2002/02/18 06:05:49; author: peter; state: Exp; lines: +58 -55
>>>Replicated Change 6659 by julian@julian_ref on 2002/02/17 22:05:13<<<
date: 2002/02/18 00:36:29; author: peter; state: Exp; lines: +10 -14
>>>Replicated Change 6647 by julian@julian_jules1 on 2002/02/17 16:34:47<<<
Setting return values into the frame has to be Machine dependent code.
date: 2002/01/30 02:31:27; author: peter; state: Exp; lines: +1 -1
>>>Replicated Change 5993 by julian@julian_ref on 2002/01/29 18:29:58<<<
Cleanup some of the suspend and single-threading code.
Can now ^Z a multithreaded process and then restart it and kill it
immediatly without getting a coredump.
all the 'suspend' code needs careful attention.
There is a vaguely-cvsweb-like http interface here:
(there is even a KSE link on the top page)
> On Mon, 18 Feb 2002, Peter Wemm wrote:
> > Matthew Dillon wrote:
> > > :
> > > :So, John's last few months of work is junk then, is it?
> > > :
> > > :Cheers,
> > > :-Peter
> > > :--
> > > :Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > >
> > > I'll tell you what is junk... patches for things like getuid() sittin
> > > in P4 (whether instrumented or not). That's junk.
> > >
> > > I'll tell what is NOT junk. What isn't junk are things like John's m
> > > complex patch to kern_descrip.c. There's real work involved there
> > > that can be salvaged, and which can be committed to the -current
> > > piecemeal if Giant is properly instrumented.
> > >
> > > The biggest problem is that all of this stuff is sitting in P4 and no
> > > of it belongs there.
> > With all due respect, bullshit! The p4 tree exists only as an alternative
> > to people having large uncommitted diffs sitting in checked out cvs trees.
> > Mailing patches between people trying to work in parallel is a bigger waste
> > of time. That is inherently single threaded.
> > Cheers,
> > -Peter
> > --
> > Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
> > "All of this is for nothing if we don't go to the stars" - JMS/B5
> > To Unsubscribe: send mail to [EMAIL PROTECTED]
> > with "unsubscribe freebsd-current" in the body of the message
Peter Wemm - [EMAIL PROTECTED]; [EMAIL PROTECTED]; [EMAIL PROTECTED]
"All of this is for nothing if we don't go to the stars" - JMS/B5
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message