• 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: CVS Support
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: CVS Support


  • Subject: Re: CVS Support
  • From: Chris Cleeland <email@hidden>
  • Date: Tue, 28 Jun 2011 13:50:39 -0500

On Tue, Jun 28, 2011 at 11:43 AM, Rodrigo Zanatta Silva
<email@hidden> wrote:
> Ok, I understand.
>
> I will have to continue using CVS. But I have a plan. I will make a
> svn/git in another server to fully work in development and every time
> we send to app store, I will comit in CVS

Better yet, consider using the git cvs wrapper.  It lets you create a
git repo from a CVS repo, and helps you commit back to CVS.

During day-to-day development you interact only with the git repo.
Only when you want to go "upstream" do you push all the way back to
CVS.

It's worked reasonably well for me on legacy projects.
 _______________________________________________
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

  • Follow-Ups:
    • Re: CVS Support
      • From: Rodrigo Zanatta Silva <email@hidden>
References: 
 >CVS Support (From: Rodrigo Zanatta Silva <email@hidden>)
 >Re: CVS Support (From: Wade Williams <email@hidden>)
 >Re: CVS Support (From: Rodrigo Zanatta Silva <email@hidden>)
 >Re: CVS Support (From: Roland King <email@hidden>)
 >Re: CVS Support (From: Scott Ribe <email@hidden>)
 >Re: CVS Support (From: Rodrigo Zanatta Silva <email@hidden>)

  • Prev by Date: Re: CVS Support
  • Next by Date: Re: CVS Support
  • Previous by thread: Re: CVS Support
  • Next by thread: Re: CVS Support
  • Index(es):
    • Date
    • Thread