As of last week, you don't have to keep your master branch in sync with
the "main" repo in order to compare against it, because the github guys
have introduced a cross-repository comparison view. The
announcement/docs on how to use it are here:
http://github.com/blog/683-cross-repository-compare-view
You can also just add the repository you're interested in and use the
"standard" git tools:
git remote add seb git://github.com/sbenthall/geonode
git fetch seb
git log origin/master...seb/mapmetadata
gitk origin/master...seb/mapmetadata
git diff origin/master...seb/mapmetadata
But of course you don't get inline comments on changesets that way.
--
David Winslow
OpenGeo - http://opengeo.org/
On 07/14/2010 11:03 AM, Sebastian Benthall wrote:
Thanks for the reviews. My fork's master branch is now updated.
On Wed, Jul 14, 2010 at 7:37 AM, Andreas Hocevar <[email protected]
<mailto:[email protected]>> wrote:
I added a couple of comments on GitHub. I hope I didn't miss
anything, because your forked master branch is still not up to
date so it's hard to compare your branch with master.
-Andreas.
On Jul 13, 2010, at 21:52 , Sebastian Benthall wrote:
> The main thing I noticed looking at this was that i18n is not
being used for a lot of the strings added. Haven't tried running
it though.
>
> Good call. Thanks, I'll fix those soon.
>
> --
> Sebastian Benthall
> OpenGeo - http://opengeo.org
>
--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
--
Sebastian Benthall
OpenGeo - http://opengeo.org
