OK, then I'm pushing what I have. Run for cover! Seriously though, it seems like I would always work this way. How often do you run into scenarios where you are glad you staged before committing?
-Alex On 3/21/13 1:54 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: > Yes, true, that's an other option I forgot because I don't use to use it > because the git way is to work with your working area and then the stage > area where you can prepare what you want in the commit, even at the "line of > a file" level, it's the first way to clean up your work, you can then > commit. > There's an other way later to clean up the commits before pushing. > > -Fred > > -----Message d'origine----- > From: Alex Harui > Sent: Thursday, March 21, 2013 9:47 PM > To: dev@flex.apache.org > Subject: Re: [OT] Log history > > > > > On 3/21/13 1:36 PM, "Frédéric THOMAS" <webdoubl...@hotmail.com> wrote: > >> ah, maybe you meant instead of the dot..., in this case I would have done >> a >> git add README >> > No, it just hasn't been my experience so far that I need to run add on files > already tracked. I'm about to push something and want to make sure I'm not > going to screw something up. > > In the flex-tlf repo I modified the build.xml and just ran "git commit > build.xml " and now "git diff remotes/origin/master" shows the right set of > changes. -- Alex Harui Flex SDK Team Adobe Systems, Inc. http://blogs.adobe.com/aharui
