Re: [RFC] git-publish

From: Junio C Hamano <junkio@cox.net>
Date: Aug 13, 2006, 19:53 UTC
Message-ID: <7vmza8l8f1.fsf@assigned-by-dhcp.cox.net>
In-Reply-To: <Pine.LNX.4.63.0608132017090.10541@wbgn013.biozentrum.uni-wuerzburg.de>

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> I'd rather have a command which tells me if I have commits after the last 
> time I pushed.

Yes.

However, I have not felt the need for "a command". In my workflow, I use tracking branches for the push destination.

Before I rewind / rebase / clean-up, I fetch from my usual push destination with these lines:

	URL: kernel.org:/pub/scm/git/git.git/
        Pull: master:refs/tags/ko-master
        Pull: next:refs/tags/ko-next
        Pull: +pu:refs/tags/ko-pu
        Pull: maint:refs/tags/ko-maint

and have a script to do this (Meta/KO -- found in "todo" branch):

	#!/bin/sh
	git fetch ko
        for i in master next pu maint
        do
        	git show-branch $i ko-$i
        done

I primarily use this to make sure I do not rewind beyond what are already pushed out, but I also can use it to see what's outstanding to be pushed.