Re: bypassing certain cvs commits
- From: "Aryeh M. Friedman" <aryeh.friedman@xxxxxxxxx>
- Date: Tue, 27 Nov 2007 10:48:04 -0500
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Then use CVS to check out the exact rev of those files that you
want. That'll make the rev be sticky in your tree, so it won't
change the next time you update. Note that I would consider it
rather rude and condescending to instruct a senior developer like
Jason on how to do backouts instead of giving him help in
identifying and maybe fixing the
problems.
I posted a extremely long and detailed set of diags to cvs-src
- --
Aryeh M. Friedman
Developer, not business, friendly
http://www.flosoft-systems.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4 (FreeBSD)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFHTDwzJ9+1V27SttsRAraaAJ9/eV10yt9q8bQSb6dY1qlhZ1h7aACdFmeO
+r3fG5dsXM/Fsr0AOU+paJk=
=LpqT
-----END PGP SIGNATURE-----
_______________________________________________
freebsd-current@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscribe@xxxxxxxxxxx"
- Follow-Ups:
- Re: bypassing certain cvs commits
- From: Peter Jeremy
- Re: bypassing certain cvs commits
- References:
- bypassing certain cvs commits
- From: Aryeh M. Friedman
- Re: bypassing certain cvs commits
- From: Eygene Ryabinkin
- Re: bypassing certain cvs commits
- From: Aryeh M. Friedman
- Re: bypassing certain cvs commits
- From: Scott Long
- bypassing certain cvs commits
- Prev by Date: Re: bypassing certain cvs commits
- Next by Date: Re: em0 panic: mutex em0 not owned
- Previous by thread: Re: bypassing certain cvs commits
- Next by thread: Re: bypassing certain cvs commits
- Index(es):
Relevant Pages
|
|