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 > >
