• 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 is examining changes during Merge so hard?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Why is examining changes during Merge so hard?


  • Subject: Re: Why is examining changes during Merge so hard?
  • From: Scott Ribe <email@hidden>
  • Date: Sun, 09 Nov 2014 07:41:06 -0700

On Nov 8, 2014, at 9:41 PM, Jerry Krinock <email@hidden> wrote:
>
> Is there an easier way to do this, or do we all do steps (1) - (3), or is my workflow wrong?

Your workflow is completely reasonable. I use SourceTree, and it makes that easy, since it displays changes inline, old code red, new code green, with a button to discard a change (I think, not that I really use that).

--
Scott Ribe
email@hidden
http://www.elevated-dev.com/
(303) 722-0567 voice





 _______________________________________________
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: Why is examining changes during Merge so hard?
      • From: Jerry Krinock <email@hidden>
References: 
 >Why is examining changes during Merge so hard? (From: Jerry Krinock <email@hidden>)

  • Prev by Date: Why is examining changes during Merge so hard?
  • Next by Date: Re: Objective Git can't link to libiconv
  • Previous by thread: Why is examining changes during Merge so hard?
  • Next by thread: Re: Why is examining changes during Merge so hard?
  • Index(es):
    • Date
    • Thread