Date: Sun, 19 Dec 2004 13:23:43 +0900 From: gnn@FreeBSD.org To: freebsd-net@FreeBSD.org Subject: Dingo and PerForce Message-ID: <m2wtveex0w.wl@minion.local.neville-neil.com>
next in thread | raw e-mail | index | archive | help
Howdy, For those who use PerForce and want to work on Dingo there is now a dingo branch, named "dingo". The dingo branch contains all of src, not just sys, as I suspect there are userland bits we'll want to do. I know I'll be doing userland things. Please make your own sub-branch off of dingo. For example, here is mine (gnn_dingo): # A Perforce Branch Specification. # # Branch: The branch name. # Update: The date this specification was last modified. # Access: The date of the last 'integrate' using this branch. # Owner: The user who created this branch. # Description: A short description of the branch (optional). # Options: Branch update options: [un]locked. # View: Lines to map source depot files to target depot files. # # Use 'p4 help branch' to see more about branch views. Branch: gnn_dingo Update: 2004/12/19 03:17:21 Access: 2004/12/19 03:17:26 Owner: gnn Description: My personal sub-branch of the dingo branch. Options: locked View: //depot/projects/dingo/sys/... //depot/user/gnn/dingo/sys/... //depot/projects/dingo/tools/... //depot/user/gnn/dingo/tools/... The main branch (dingo) is locked against changes and, more importantly, accidental deletion. Let me know if there are any issues with any of this. Oh, and the integration from vendor to dingo was done last Saturday night around 23:00 JST. Later, George
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?m2wtveex0w.wl>