rspec users - Apr 2008 - Has anyone pulled from the repo recently, but not on/after 4/16?

I screwed up the repo on github and a bunch of commits are missing.
So I''m hoping that there are a couple people out there that have
pulled fairly recently (ideally on 4/15), but not today.  If so, can
you please tar up your entire rspec-dev project and email it to me so
I can try to fix this?

Please do NOT update your repo to get the latest changes at this point.

Pat

Pat Maddox wrote:
> I screwed up the repo on github and a bunch of commits are missing.
> So I''m hoping that there are a couple people out there that have
> pulled fairly recently (ideally on 4/15), but not today.  If so, can
> you please tar up your entire rspec-dev project and email it to me so
> I can try to fix this?
>
> Please do NOT update your repo to get the latest changes at this point.
>
> Pat
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>   
Pat, I forked the rspec repos on git hub.  The last time I synced up 
with the official ones was on 4-12-08.  You can my tars from git hub:
http://github.com/bmabey

You will have to cherrypick certain commits up until 4-15.  You will 
also need to remove one of my commits (rspec-rails only), but that 
should be pretty easy.

If you want help with this using my repos let me know, I''d be glad to
help.

-Ben

> I screwed up the repo on github and a bunch of commits are missing.
> So I''m hoping that there are a couple people out there that have
> pulled fairly recently (ideally on 4/15), but not today.  If so, can
> you please tar up your entire rspec-dev project and email it to me so
> I can try to fix this?
Pat, please don''t accept blame for this.  You didn''t screw up
the
repo: git screwed up the repo by rewriting history when it shouldn''t.

-Steven

On Apr 16, 2008, at 1:03 PM, Steven Baker wrote:
>> I screwed up the repo on github and a bunch of commits are missing.
>> So I''m hoping that there are a couple people out there that
have
>> pulled fairly recently (ideally on 4/15), but not today.  If so, can
>> you please tar up your entire rspec-dev project and email it to me so
>> I can try to fix this?
>
> Pat, please don''t accept blame for this.  You didn''t
screw up the
> repo: git screwed up the repo by rewriting history when it
shouldn''t.
Absolutely. +1000
>
>
> -Steven
>
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users

On Wed, Apr 16, 2008 at 10:03 AM, Steven Baker <steven at
stevenrbaker.com> wrote:
> > I screwed up the repo on github and a bunch of commits are missing.
>  > So I''m hoping that there are a couple people out there that
have
>  > pulled fairly recently (ideally on 4/15), but not today.  If so, can
>  > you please tar up your entire rspec-dev project and email it to me so
>  > I can try to fix this?
>
>  Pat, please don''t accept blame for this.  You didn''t
screw up the
>  repo: git screwed up the repo by rewriting history when it
shouldn''t.
Blame is irrelevant here.  Code and commit history is gone, and we
need to get it back.  We also need to figure out how to prevent this
from happening again.  That''s all.

Pat

I might be of some help ...

The last time I pulled the rspec was like Saturday or Sunday. I will
tar up my rspec directory and send it over when I get home in a few
hours.

On 4/16/08, Pat Maddox <pergesu at gmail.com>
wrote:
> On Wed, Apr 16, 2008 at 10:03 AM, Steven Baker <steven at
stevenrbaker.com>
> wrote:
> > > I screwed up the repo on github and a bunch of commits are
missing.
> >  > So I''m hoping that there are a couple people out there
that have
> >  > pulled fairly recently (ideally on 4/15), but not today.  If so,
can
> >  > you please tar up your entire rspec-dev project and email it to
me so
> >  > I can try to fix this?
> >
> >  Pat, please don''t accept blame for this.  You
didn''t screw up the
> >  repo: git screwed up the repo by rewriting history when it
shouldn''t.
>
> Blame is irrelevant here.  Code and commit history is gone, and we
> need to get it back.  We also need to figure out how to prevent this
> from happening again.  That''s all.
>
> Pat
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users
>

-- 
Bryan Ray
http://www.bryanray.net

"Programming today is a race between software engineers striving to
build bigger and better idiot-proof programs, and the Universe trying
to produce bigger and better idiots. So far, the Universe is winning."

Actually, if you updated the repo after 4/16, please send it to me.
Also include any winning lotto numbers for the date of your last pull.
 In fact, screw the repo, I just want the lotto numbers.

You might try here
http://www.google.com.au/intl/en/gday/index.html

Jonathan


On Apr 16, 2008, at 3:23 PM, Pat Maddox wrote:
> Actually, if you updated the repo after 4/16, please send it to me.
> Also include any winning lotto numbers for the date of your last pull.
>  In fact, screw the repo, I just want the lotto numbers.
> _______________________________________________
> rspec-users mailing list
> rspec-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/rspec-users