Thread (1 message) 1 message, 1 author, 2016-06-15
  • (off-list ancestor, not in this archive)
  • Re: [RFC] git-publish · Junio C Hamano <hidden> · 2016-06-15

Re: [RFC] git-publish

From: Junio C Hamano <hidden>
Date: 2016-06-15 22:42:36

Johannes Schindelin [off-list ref] 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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help