git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Felipe Contreras <felipe.contreras@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: RE: What's cooking in git.git (Apr 2014, #03; Fri, 11)
Date: Fri, 11 Apr 2014 18:27:53 -0500	[thread overview]
Message-ID: <53487a78f38bf_3b596b93106e@nysa.notmuch> (raw)
In-Reply-To: <xmqq1tx3qzel.fsf@gitster.dls.corp.google.com>

Junio C Hamano wrote:
> * 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.

>  - 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'.

> * 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

  reply	other threads:[~2014-04-11 23:37 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-04-11 22:22 What's cooking in git.git (Apr 2014, #03; Fri, 11) Junio C Hamano
2014-04-11 23:27 ` Felipe Contreras [this message]
2014-04-12  6:49   ` Junio C Hamano
2014-04-12 18:29 ` Ramsay Jones
2014-04-15 16:45   ` Junio C Hamano
2014-04-15 23:18     ` Duy Nguyen
2014-04-16 11:31       ` Ramsay Jones
2014-04-13 20:18 ` Michael Haggerty
2014-04-17 16:52 ` W. Trevor King
2014-04-17 17:52   ` Junio C Hamano

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=53487a78f38bf_3b596b93106e@nysa.notmuch \
    --to=felipe.contreras@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).