git/list[1] front-page[2] threads[3] people[4] search[5] about
 

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.

Previous: Max Horn
Message 11 of 11 in “What's cooking in git.git (Feb 2014, #06; Wed, 19)”
  1. Junio C HamanoFeb 19, 2014
  2. Max HornFeb 20, 2014
  3. Junio C HamanoFeb 20, 2014
  4. Max HornFeb 21, 2014
  5. Torsten BögershausenFeb 21, 2014
  6. Junio C HamanoFeb 21, 2014
  7. Max HornFeb 22, 2014
  8. Junio C HamanoFeb 24, 2014
  9. Junio C HamanoFeb 24, 2014
  10. Max HornFeb 24, 2014
  11. Ramkumar RamachandraFeb 21, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.