Re: Xcode 4.2.1 Git can't commit
Re: Xcode 4.2.1 Git can't commit
- Subject: Re: Xcode 4.2.1 Git can't commit
- From: Chris Cleeland <email@hidden>
- Date: Tue, 29 Nov 2011 17:15:34 -0600
On Tue, Nov 29, 2011 at 4:51 PM, Richard Wackerbarth <email@hidden> wrote:
> On Nov 29, 2011, at 4:13 PM, Bill Cheeseman wrote:
>> That's the essence of my problem with Git. I'm one of those developers (I suspect there are many of us) who can use the command line but aren't really comfortable with it.
>
> Bill,
> From your prior description using dated zip files, I can assure you that you don't need to know much about git, in order to use it to accomplish equivalent capability.
>
> Adding a tag to a particular tracking point is isomorphic to creating an archive of the particular state of the files.
> (Although you will probably find doing so unnecessary since the state after each and every commit remains readily available.)
> And, if you use a GUI such as GitX, diff-ing between any two tracking points is as easy as, if not easier than, specifying the files to "FileMerge".
>
> I don't think that you should have to spend (a) any time in the command-line git, or (b) more than a few minutes learning to use a GUI access to a git repository.
>
This assertion is correct for the common case, but not for special
situations such as what Bill originally encountered. For situations
outside the mainstream, it's unlikely that a GUI will provide a rich
enough interface to enable you to express precisely what's needed.
git (and most other VCS) are so feature-rich; GUIs over the top of
them only provide access to a subset of functionality.
But, you're correct that for the day-to-day operations of making a
change, committing that change, creating a branch, tagging, etc., that
all can be handled comfortably from within a GUI and likely with far
more aplomb than creating dated zipfiles.
> Remember that a git repository is much like a data base. You can access it via any of a number of different mechanisms (Xcode, a Git GUI, the git command line, ...) and any changes made by one access method are immediately available to all of the others.
>
Carrying this analogy further, often with a database it's really easy
to get some data out and that can probably be done with a GUI. But,
if you need to do crazy outer joins and the like, then you may have to
dip down to the level of SQL.
> I know that it may be a new idea to you, but I've been using version control systems for (literally) forty years. I strongly suggest that you expend an hour or two and "modernize" your workflow. The tools available today are much more powerful, but also easier to use (at least in a superficial manner) than anything we had available "way back then".
>
stackoverflow.com has a lot of good questions (and answers) on git and
other VCS. I use it frequently and take notes for the more esoteric
activities.
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden