Question on for-each-ref and --contains

in rev-list directly)? If yes, then probably also the --(no-)merged options, but hopefully with the arbitrary commit this time? Thank you in advance, Blind. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More m

Re: [RFC/PATCH] Introduce branch..pushremote

anches which are not there already. push --all on other hand pushes .. all (as expected :-))... Its difficult for me to manage quickly, lets say, "news-to-push/*" and "crazy-ideas/*" branches ... Blind. -- To unsubscribe from this list: send the line "unsubscribe git&quo

Re: [RFC/PATCH] Introduce branch..pushremote

the case. ... or branch..pushremote can support some kind of a "none" value? Blind. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html

Re: [RFC/PATCH] Introduce branch..pushremote

marked as special with branch..pushremote, then it could be logical to push it only when is explicitly specified on the command line (excluded from --all)? Thanks, Blind. 2013/2/8 Ramkumar Ramachandra : > This new configuration variable overrides the remote in > `branch..remote` for pushes.