From: Jeff King <peff@peff.net>
To: Philip Oakley <philipoakley@iee.org>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Ramkumar Ramachandra <artagnon@gmail.com>
Subject: Re: What's cooking in git.git (Mar 2014, #03; Fri, 14)
Date: Tue, 18 Mar 2014 00:40:16 -0400 [thread overview]
Message-ID: <20140318044016.GA8240@sigill.intra.peff.net> (raw)
In-Reply-To: <EA1EF5746EA7414CAE1320AA61100178@PhilipOakley>
On Sun, Mar 16, 2014 at 06:30:49PM -0000, Philip Oakley wrote:
> >* 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.
>
> To me 'publish' didn't fel right, though the later 'push' suggestion felt
> honest.
> (http://git.661346.n2.nabble.com/RFC-PATCH-format-patch-introduce-branch-forkedFrom-tp7601682p7603725.html)
FWIW, I think I like "@{push}" at this point, and we should perhaps add
"@{pull}" as an alias for "@{upstream}" for consistency.
-Peff
prev parent reply other threads:[~2014-03-18 4:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-14 22:09 What's cooking in git.git (Mar 2014, #03; Fri, 14) Junio C Hamano
2014-03-15 8:15 ` Torsten Bögershausen
2014-03-17 17:01 ` Junio C Hamano
2014-03-19 10:53 ` Max Horn
2014-03-19 12:32 ` Max Horn
2014-03-19 17:04 ` Junio C Hamano
2014-03-19 17:21 ` Max Horn
2014-03-19 18:53 ` Junio C Hamano
2014-03-15 12:34 ` Duy Nguyen
2014-03-17 18:05 ` Junio C Hamano
2014-03-16 18:30 ` Philip Oakley
2014-03-16 23:15 ` Ramkumar Ramachandra
2014-03-17 18:01 ` Junio C Hamano
2014-03-17 22:41 ` Philip Oakley
2014-03-17 17:21 ` Junio C Hamano
2014-03-18 0:16 ` Philip Oakley
2014-03-18 4:40 ` Jeff King [this message]
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20140318044016.GA8240@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=philipoakley@iee.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).