• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Why does SCM have to be so ....... hard?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why does SCM have to be so ....... hard?


  • Subject: Re: Why does SCM have to be so ....... hard?
  • From: Wade Tregaskis <email@hidden>
  • Date: Sun, 19 Sep 2004 11:11:47 +1000

Perhaps you are overlooking the fact that this would only be useful for single-person-projects and completely useless in a project with two or more developers?

Possibly, but looking at it it differently, let's say this mechanism was for a local SCM which then could connect itself to the "real" remote repository?

Are there any viable products which do this today? I know of one person who wrote a bridge for connecting multiple CVS repositories (on remote machines) - which worked to a point - but I'm not aware of such functionality present natively even in the commercial offerings...


I don't quite see why the current implementation would have a zero usefulness for you?

Well, it's a whole lot easier to simply duplicate my whole project directory when I have a finished version than work with CVS etc. I can just as easy run a diff on a whole directory.


Of course, if I would commit on a regular basis then it would be useful, but since you have to do all these things manually I am a whole lot less likely to actually get around to creating versions regularly.

What you seem to be ignoring is the need for commit comments... what's the point of having a thousand versions of a file if you can't possibly find which one you want? And having to write a comment for every file every time you save it seems very counter-productive, if you save frequently as I (and I hope others) do.*


Granted, in the system you're looking for with your two-tier SCM you could probably get away with no [or few] comments in your local repository. But even though you could diff your latest against the remote repository to remind yourself what changed, you may miss some of the subtleties you've since forgotten.

Wade Tregaskis (aim & yahoo: wadetregaskis, icq: 40056898, msn & email: email@hidden, jabber: email@hidden)
-- Sed quis custodiet ipsos custodes?


* = I should say here that I used to save almost every line when using XCode 1.0 through 1.2, but 1.5 has been pretty much flawless (in terms of crashing). Since I've complained about XCode on-list before, it's only fair that I now thank the XCode team for their work in 1.5 - I at last am finally pretty happy with it (which, if you haven't picked up on how cynical & pedantic I am, is quite an achievement). :)

_______________________________________________
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


References: 
 >Why does SCM have to be so ....... hard? (From: Christoffer Lerno <email@hidden>)
 >Re: Why does SCM have to be so ....... hard? (From: j o a r <email@hidden>)
 >Re: Why does SCM have to be so ....... hard? (From: Christoffer Lerno <email@hidden>)

  • Prev by Date: Re: Why does SCM have to be so ....... hard?
  • Next by Date: Re: Why does SCM have to be so ....... hard?
  • Previous by thread: Re: Why does SCM have to be so ....... hard?
  • Next by thread: Re: Why does SCM have to be so ....... hard?
  • Index(es):
    • Date
    • Thread