Cellbe:Community Portal

From Cellbe

Revision as of 15:43, 23 November 2012 (edit) 12.198.104.86 (Talk) (FFTibqkqUtEHPtr) ← Previous diff		Revision as of 16:13, 23 November 2012 (edit) (undo) 212.68.90.12 (Talk) (nyjvQkbafuOeH) Next diff →
Line 1:		Line 1:
-	Dear Sally,   Hello!  I totally miss senieg you on QVC with Birkenstocks!  You would truly liven the show up and made QVC fun to watch.  I do not know what is going on with QVC, but the vendor they have chosen to represent their Birkenstock product is boring-Claudia.  She may be a nice person, but the show is boring.  I understand you were on QVC in January or February, but I missed senieg you on TV.  Will you be on QVC ever again?  Could you please tell me what is going on with QVC?  My mom and I really enjoyed watching you and you made us laugh, and made the show a lot more interesting.  Not only that, you were interesting to watch and I do not understand why you left. I heard you were selling your own products on QVC?  Is this correct?  Let me know what is happening for the future with you and the Q.  Talk to you soon.  Katrina from Clearwater, Florida	+	As Robert notes, you can do:svn merge -c-Xwhere X is the single rivesion the change happened.  the -c is to specify a single rivesion, and leading the rivesion with a '-' indicates it should be reversed.Ash, that's just wrong! The whole point of rivesion control is that it should maintain a complete history of the changes to your code.  The metadata associated with each change (the log message, for example) is invaluable in explaining *why* something was done, or why it was wrong.  It's one of the major problems I have with most dvcs (git, darcs, etc) solutions; it becomes possible to lose rivesions and revise history.

---

Revision as of 16:13, 23 November 2012

As Robert notes, you can do:svn merge -c-Xwhere X is the single rivesion the change happened. the -c is to specify a single rivesion, and leading the rivesion with a '-' indicates it should be reversed.Ash, that's just wrong! The whole point of rivesion control is that it should maintain a complete history of the changes to your code. The metadata associated with each change (the log message, for example) is invaluable in explaining *why* something was done, or why it was wrong. It's one of the major problems I have with most dvcs (git, darcs, etc) solutions; it becomes possible to lose rivesions and revise history.