Message: previous - next
Month: April 2012

Re: [trinity-devel] TIME Frame 3/29 -> 4/10 kwrite crash introduced

From: "David C. Rankin" <drankinatty@...>
Date: Mon, 30 Apr 2012 21:56:55 -0500
On 04/30/2012 06:34 PM, Darrell Anderson wrote:
> I don't know how this is supposed to work. I ran 'git reset --hard'. When I viewed the top level with git log, the newest date was April 10. Seemed okay to me.
> After my previous two builds and testing I wondered whether that truly reset the source files. I changed to the tdebase directory and again ran git log. The most recent commit was from a few days ago.
> So I did a git reset there too and in tdelibs.
> In light of this, I don't think my previous build runs and tests were credible because more than likely I was building at least tdelibs and tdebase with recent sources.
> There must be a way to correctly reset my sources so I build with the sources from that date and ignore all commits thereafter. I love wasting my time.
> Darrell


  I thought I had this, now I'm confused (happens). Just so I'm keeping up,
since I create tarballs from the tree before building -- what kind of reset do I

GIT = (Great Indecipherable Technology)

  In theory backing up should be simple, but I've never done it. Whatever reset
we do has to back out all the updates from that point forward so when I step
through the tree and create tarballs, I get what I'm supposed to get when I tar
the source up.

  Do we have a consensus on Tim's:

git reset --hard HEAD
git checkout <hash>

executed from within each module?

  OK, I'm going with this :)

David C. Rankin, J.D.,P.E.