On Nov 29, 2012, at 9:48 AM, Kyle Sluder <k...@ksluder.com> wrote: > On Thu, Nov 29, 2012, at 03:51 AM, Charles Srstka wrote: >> On Nov 29, 2012, at 4:39 AM, "jonat...@mugginsoft.com" >> <jonat...@mugginsoft.com> wrote: >> >>> Interactive rebasing is quite straightforward. >>> >>> # fiddle with the last 10 commits >>> git rebase -i HEAD~10 >> >> I think that what Greg was referring to was the fact that it can't be >> done from within Xcode without dropping down to the Terminal, which is >> something that the Xcode team could certainly fix. > > How about we get them to fix the IDE before we have them write a git GUI?
Well, Xcode already provides a partial git GUI... >> >>> I also subscribe to the commit small and often philosophy. >>> If I don't I tend to end up with a ball of changes that ultimately get >>> committed under some very vague title as I have forgotten the detail of >>> what I was doing. >> >> That's exactly my experience as well. Then one of those changes in the >> commit causes a side-effect, and on looking back on the change that >> caused it, you can't remember what specifically it was supposed to do in >> the first place. > > One might argue that it would be a good idea for Xcode to offer the > ability to commit snapshots to a branch on the git repo to which all the > affected files belong, if one such repo exists. That seems a lot less of > a burden that writing a wrapper for interactive rebase. That works. This, too, would be more efficient than having a whole separate repository. Charles _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
