Archive:Development/Tutorials/Git/BestPractices: Difference between revisions

Revision as of 14:07, 1 March 2011

Warning

This page is yet to be reviewed for changes required by the migration to Git. Information and commands on this page may no longer be valid and should be used with care. Please see the KDE Git hub page for more details.

Git allows us to do a lot of things that svn doesn't. However... just because you *can*, doesn't mean you *should*. ;) Here's a list of suggestions for using git without headaches.

TODO:

merge squash: when and how to rewrite history
merge requests vs. pushing

Revision as of 02:16, 2 November 2009 (view source) Chani (talk \| contribs) (Created page with 'Git allows us to do a lot of things that svn doesn't. However... just because you can, doesn't mean you should. ;) Here's a list of suggestions for using git without headache...')		Revision as of 14:07, 1 March 2011 (view source) Odysseus (talk \| contribs) No edit summary Newer edit →
Line 1:		Line 1:
			{{warning\|This page is yet to be reviewed for changes required by the migration to Git. Information and commands on this page may no longer be valid and should be used with care. Please see the [[Development/Git\|KDE Git hub page]] for more details. }}

	Git allows us to do a lot of things that svn doesn't. However... just because you can, doesn't mean you should. ;) Here's a list of suggestions for using git without headaches.		Git allows us to do a lot of things that svn doesn't. However... just because you can, doesn't mean you should. ;) Here's a list of suggestions for using git without headaches.