Personally, I loathe Git. Maybe it's just that I'm old school or have grown used to SVN, but every time I use Git, I get lost. Branch, merge, push, pull, clone, and pray don't screw up because you'll be in a rat-hole that has no end. "But just issue commands X, Y, Z. Followed by A, B, C. Oh, and by the way, if you issue C before B you're totally screwed".
Sorry, but I've never seen a good argument for Git that doesn't include "but it supports a distributed development setup". Why is that superior to what we already to with SVN? Our branching etc. seems to work fine. If someone could outline, in concrete terms, the workflow that would make Git help make my life easier, or outline why staying with SVN is going to slow people down or turn people off, it would be a great help. Otherwise, -1 from me. FWIW, Erick On Jan 3, 2014 6:29 PM, "Michael Della Bitta" < michael.della.bi...@appinions.com> wrote: > Aha, gotcha. Thanks for elucidating. > > Michael Della Bitta > > Applications Developer > > o: +1 646 532 3062 | c: +1 917 477 7906 > > appinions inc. > > “The Science of Influence Marketing” > > 18 East 41st Street > > New York, NY 10017 > > t: @appinions <https://twitter.com/Appinions> | g+: > plus.google.com/appinions<https://plus.google.com/u/0/b/112002776285509593336/112002776285509593336/posts> > w: appinions.com <http://www.appinions.com/> > > > On Fri, Jan 3, 2014 at 1:19 PM, Robert Muir <rcm...@gmail.com> wrote: > >> On Fri, Jan 3, 2014 at 1:15 PM, Michael Della Bitta >> <michael.della.bi...@appinions.com> wrote: >> >> My working directory _IS NOT_ clean if 'git push' would do something. >> > >> > I just wanted to make sure you understand this... 'git push' operates >> > between your local repository and the remote repository you specify, >> and not >> > on working directories, right? 'git status' comes up clean because >> there are >> > no pending changes between your working directory and your local repo. >> > >> >> thats really not the issue here: git status will list the pending >> commits if you force the merge not to use fast-forward. >> >> the issue is fast-forward merges. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org >> For additional commands, e-mail: dev-h...@lucene.apache.org >> >> >
