On Jul 28 13:00, Garrett Cooper wrote:
> On Mon, Jul 28, 2008 at 12:25 PM, Nate Straz <[EMAIL PROTECTED]> wrote:
> >  6109 files changed, 25452 insertions(+), 645242 deletions(-)
> >
> > It looks like you remove a lot of ballista open_hpi_testsuite, and
> > open_posix_testsuite.  Was that intended?
> 
> No, the remove wasn't intended for open_{hpi,posix}*, nor most of the
> stuff in ballista. I'm still trying to work out the git stuff because
> this is my first crack at it.

Git takes a different mindset to use than CVS or Subversion.  I'm still
getting the hang of it too.  A few key ideas which might be useful to
pass on:

1. You need to make sure you add things to the "commit" before you
do "git commit."  "git status" will show you everything that's changed
and what "git commit" will skip over.

2. Getting back to a clean tree can take a few more steps than 
"svn revert -R."  I find myself using "git reset --hard; git clean -d"
to get back to where I started.

3. You can always create a new branch from before you started to screw
up.  Just "git checkout -b new <sha1>" and you can start over.

4. In git, the revision history is changeable.  All you need to do is
create a new branch, do it right, then rename the new branch over the
old branch.

> Even if you run make clean for ballista though it leaves binaries
> laying around though which bloat the snapshots that are taken monthly
> (blexer, bparser, etc). That's where part of the removal there comes

That sounds like a good candidate for a separate patch.

Nate

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
_______________________________________________
Ltp-list mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/ltp-list

Reply via email to