Date: Sun, 19 Dec 2004 18:20:17 +0100 From: Max Laier <max@love2party.net> To: freebsd-net@freebsd.org Cc: gnn@freebsd.org Subject: Re: Dingo and PerForce Message-ID: <200412191820.23664.max@love2party.net> In-Reply-To: <m2wtveex0w.wl@minion.local.neville-neil.com> References: <m2wtveex0w.wl@minion.local.neville-neil.com>
next in thread | previous in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] On Sunday 19 December 2004 05:23, gnn@FreeBSD.org wrote: > 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): <...> > 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. I am not all that familiar with perforce so I am wondering: What is the benefit of having this branch if it will be tracking HEAD anyway, we can just branch off the normal vendor branch. Or do you plan to integrate parts back? I have 'mlaier_carp2' off the vendor branch. What will be the benefit if I move it to 'dingo' instead? -- /"\ Best regards, | mlaier@freebsd.org \ / Max Laier | ICQ #67774661 X http://pf4freebsd.love2party.net/ | mlaier@EFnet / \ ASCII Ribbon Campaign | Against HTML Mail and News [-- Attachment #2 --] -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (FreeBSD) iD8DBQBBxbhXXyyEoT62BG0RAufyAJ45BCwprf3VbLqZoeDK2Qbx4fa5EQCaA7Mm HBWeKMe4jvOY67UCLbmVeb8= =am+I -----END PGP SIGNATURE-----
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200412191820.23664.max>