Re: bypassing certain cvs commits

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wes Morgan wrote:
On Tue, 27 Nov 2007, Aryeh M. Friedman wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

As per my detailed comments to Jason
http://lists.freebsd.org/pipermail/cvs-src/2007-November/084307.html
is broken but I want to update everything else how do I by pass the
ref'ed commit?


You do realize that running -current, especially so soon after a
branch, is virtually expected to have this kind of breakage from
time to time, sometimes frequently. The best and most productive
course of action would probably be to contact the committer directly
rather than creating a lot of unneeded chatter on multiple mailing
lists.

I contacted him directly after tracking the problem down my only
question was backing out (which was answered)... I am well aware of
the drawbacks of tracking stuff so closely but since I don't have time
to do coding I have decided to do my best to be a early real world tester.

Unless there is some critical "must-have" feature in -current that
isn't available in the 7-stable tree, perhaps you'd be better off
tracking that instead. 7.0 is going to be fantastic, and I have not
yet seen anything committed to -current that would make me want to
track it instead of 7, and I've tracked -current since 4-current.

There are some hardware issues that are only fixed (not completely so
I might add... some of them are still using yet to be committed
patches) 8-current.. also since I am attempting to learn everything I
can about OS development tracking 8-current so closely defently helps
me understand the process better... an other reason is I can deal with
the occasional downtime as long I know how to backout of stuff (which
I didn't learn to last night) so I would like to be in the camp of
"yes I know it" before it is even offically out.


WNM



- --
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

iD8DBQFHTOAVJ9+1V27SttsRAuZnAJsFvM0U1NgWOnepuWO42InqxrA7WwCeMEzu
Ojp0qee+w+N4CMylv1aSl3E=
=TfQS
-----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"

Relevant Pages

  • Re: [PATCH] Support for Dell D630 sound
    ... |> Hash: SHA1 ... Could you or may I commit against -HEAD? ... | from Ariff soon, would someone please commit. ...
    (freebsd-current)
  • Re: bypassing certain cvs commits
    ... Hash: SHA1 ... As per my detailed comments to Jason ... ref'ed commit? ... The best and most productive course of action would probably be to contact the committer directly rather than creating a lot of unneeded chatter on multiple mailing lists. ...
    (freebsd-current)
  • Re: bypassing certain cvs commits
    ... Hash: SHA1 ... Eygene Ryabinkin wrote: ... ref'ed commit? ... Grab the diff and revert if by hand after CVSup? ...
    (freebsd-current)
  • Re: gdbserver on latest -STABLE ...
    ... Hash: SHA1 ... Is this related to the commit that just went through to enable on arch that ... support it? ...
    (freebsd-stable)
  • Re: [stable] [patch 44/47] pxamci: fix byte aligned DMA transfers
    ... I don't know why it has a different SHA1 in the mmc tree, ... it would have had the same commit in the kernel too. ... Most likely a rebase. ...
    (Linux-Kernel)