On 3/23/13 10:07 AM, "Michael A. Labriola" <labri...@digitalprimates.net>
wrote:
>> OK, nice story. But for me, I have no idea how you "pull in his changes and
>> review". Or "go back and test against unmodified code". And are you
>> stashing or committing your changes first? What git commands and >flags do
>> you use?
>
>> And the main debate is: if you have a simple change to the README, are you
>> creating a branch for that?
>
> Another quick aside, I understand the value of keeping this all in email and
> searchable too, but if we wanted to, I wouldn't mind setting up a connect
> session or similar at some point where we could go through examples against
> the actual SDK in real time, show common tasks, what the git status looked
> like and discuss procedure. We could always record it for other to watch too.
> Its just a thought, but I am certainly open to answering each one here.
For me, I don't need a video (even though you are always entertaining). I'm
actually at the point where I think I have a enough knowledge to be
successful and am mostly refining my understanding.
It kind of bugs me that there are multiple ways to do things in Git (stash
or don't stash, add or direct commit) and it represents a vastly different
way of thinking than SVN, VSS or Perforce, but so far, I'm liking it.
--
Alex Harui
Flex SDK Team
Adobe Systems, Inc.
http://blogs.adobe.com/aharui
