*: stop using 0xBEEF

Using 0xBEEF is annoying in examples because it makes it makes it look like
the user can use ascii or something. In the Procfile use 0x0,0x1,0x2,etc and
use 0xBAD0 in test.
Fixed via 24fd126


On Tue, Sep 9, 2014 at 4:39 PM, Jonathan Boulle <notifications@github.com>
wrote:

> In wal/wal_test.go:
>
> > @@ -158,7 +158,7 @@ func TestRecover(t *testing.T) {
> >  	if err != nil {
> >  		t.Fatal(err)
> >  	}
> > -	i := &raftpb.Info{Id: int64(0xBEEF)}
> > +	i := &raftpb.Info{Id: int64(0xBAD0)}
>
> missed one on line 278 ;-)
>
> —
> Reply to this email directly or view it on GitHub
> <https://github.com/coreos/etcd/pull/1038/files#r17335404>.
>