Re: What's cooking in git.git (Feb 2014, #06; Wed, 19)
- From
Ramkumar Ramachandra <artagnon@gmail.com>
- Date
- Feb 21, 2014, 16:18 UTC
- Message-ID
- <CALkWK0ktd1c-KGc6AqqYNE=_skQGdA0bu4T7yx-2iiPOibSfuA@mail.gmail.com>
- In-Reply-To
- <xmqqppmi7pbn.fsf@gitster.dls.corp.google.com>
Junio C Hamano wrote:
Show 14 quoted lines
> * jk/branch-at-publish-rebased (2014-01-17) 5 commits
> - t1507 (rev-parse-upstream): fix typo in test title
> - implement @{publish} shorthand
> - branch_get: provide per-branch pushremote pointers
> - branch_get: return early on error
> - sha1_name: refactor upstream_mark
>
> Give an easier access to the tracking branches from "other" side in
> a triangular workflow by introducing B@{publish} that works in a
> similar way to how B@{upstream} does.
>
> Meant to be used as a basis for whatever Ram wants to build on.
>
> Will hold.Since I've decided that I don't have the time to work on this, we've added this to the list of project ideas for GSoC 2014 (http://git.github.io/SoC-2014-Ideas.html). Hopefully, a student will come along and volunteer to finish this.