RE: What's cooking in git.git (Apr 2014, #03; Fri, 11)

From: Felipe Contreras <felipe.contreras@gmail.com>
Date: Apr 11, 2014, 23:27 UTC
Message-ID: <53487a78f38bf_3b596b93106e@nysa.notmuch>
In-Reply-To: <xmqq1tx3qzel.fsf@gitster.dls.corp.google.com>

Junio C Hamano wrote:

Show 8 quoted lines

> * fc/complete-aliased-push (2014-04-09) 1 commit
>  - completion: fix completing args of aliased "push", "fetch", etc.
> 
>  Will merge to 'next'.
> 
> 
> * fc/remote-helper-fixes (2014-04-09) 4 commits
>  - remote-bzr: include authors field in pushed commits

Before you do, you might want to pick the unrelated fix I just sent[1], otherwise this test might fail on some machines.

Show 5 quoted lines

>  - remote-bzr: add support for older versions
>  - remote-hg: always normalize paths
>  - remote-helpers: allow all tests running from any dir
> 
>  Will merge to 'next'.

Show 14 quoted lines

> * fc/publish-vs-upstream (2014-04-11) 8 commits
>  - sha1_name: add support for @{publish} marks
>  - sha1_name: simplify track finding
>  - sha1_name: cleanup interpret_branch_name()
>  - branch: display publish branch
>  - push: add --set-publish option
>  - branch: add --set-publish-to option
>  - Add concept of 'publish' branch
>  - t5516 (fetch-push): fix test restoration
> 
>  Add branch@{publish}; this round v3 hasn't yet seen much reviews
>  yet.
> 
>  Seems to have some interactions to break tests when merged to 'pu'.

That was v2, wasn't it?

[1] http://article.gmane.org/gmane.comp.version-control.git/246157

-- 
Felipe Contreras