Re: [orca-list] Keeping your orca git tree up to date.

[Steve Holmes <steve holmes88 gmail com>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: RIPEMD160

These five steps sound a lot harder than "git-pull." Is there some
reason that git-pull of Orca does not pull the most recent changes?

On Mon, Jun 01, 2009 at 10:45:09AM +1000, Luke Yelavich wrote:
> Hi all
> Here is one way that you can keep your orca git tree up to date. Note that this method is likely to delete any build files you have lying around, so you will very likely have to rebuild orca from scratch, including the ./autogen.sh step.
> 
> 1. Go into your orca git tree.
> 2. Run "git fetch origin"
> 3. Run "git checkout origin"
> 4. Run "git branch -f master origin"
> 5. Run "git checkout master"
> 
> This assumes you have no local patches committed against the orca tree, in which case you will have to rebase. If there are enough people who want to know this, I will write a quick guide on how to rebase your changes on the latest orca code.
> 
> hth
> 
> Luke
> _______________________________________________
> Orca-list mailing list
> Orca-list gnome org
> http://mail.gnome.org/mailman/listinfo/orca-list
> Visit http://live.gnome.org/Orca for more information on Orca.
> The manual is at http://library.gnome.org/users/gnome-access-guide/nightly/ats-2.html
> The FAQ is at http://live.gnome.org/Orca/FrequentlyAskedQuestions
> Netiquette Guidelines are at http://live.gnome.org/Orca/FrequentlyAskedQuestions/NetiquetteGuidelines
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)

iEYEAREDAAYFAkonUsEACgkQWSjv55S0LfHzlQCfZbGrIscDwU+IyA4fi6NZbO5T
kroAn1a9SkHmaFp0ILirdako+XkfznYY
=PlHR
-----END PGP SIGNATURE-----