On Thu, Nov 29, 2012, at 11:16 AM, Charles Srstka wrote: > On Nov 29, 2012, at 1:08 PM, Kyle Sluder <k...@ksluder.com> wrote: > > > On Nov 29, 2012, at 10:47 AM, Charles Srstka <cocoa...@charlessoft.com> > > wrote: > > > >> On Nov 29, 2012, at 9:48 AM, Kyle Sluder <k...@ksluder.com> wrote: > >> > >>> > >>> 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. > > > > Well, it only works if all the source files belong to the same repo. It > > fails in the presence of submodules or disparate checkouts. > > Why couldn't you add a branch to each individual repo and commit the > files to each as necessary?
What's your mechanism for tying all these repos together so that when you roll back a snapshot it happens atomically across all files? If Xcode's gonna muck with my repo, I want to be able to revert it. That's kind of the essence of version control. --Kyle Sluder _______________________________________________ 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
