git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: git@vger.kernel.org
Subject: [PATCH v2 0/12] implement @{push} shorthand
Date: Fri, 1 May 2015 18:44:15 -0400	[thread overview]
Message-ID: <20150501224414.GA25551@peff.net> (raw)

This is a re-roll of the series at:

  http://thread.gmane.org/gmane.comp.version-control.git/266532

There were some minor fixes in response to review, but the main change
here is support for "git for-each-ref --format=%(push)". To do that, I
pulled the push logic into remote.[ch], where it can be used from both
sha1_name.c and for-each-ref.c. This is a better place for it to reside,
anyway, and may help in the future unifying it with the other remote
code that is used by `git push`.

In an effort to reuse as much of the @{upstream} code as possible, I did
similar refactoring for that side; we now have branch_get_upstream().
Even though the logic for getting @{upstream} isn't nearly as
complicated as for @{push}, I think several call-sites are improved by
using the new helper.

  [01/12]: remote.c: drop default_remote_name variable
  [02/12]: remote.c: drop "remote" pointer from "struct branch"
  [03/12]: remote.c: hoist branch.*.remote lookup out of remote_get_1
  [04/12]: remote.c: provide per-branch pushremote name
  [05/12]: remote.c: introduce branch_get_upstream helper
  [06/12]: remote.c: report specific errors from branch_get_upstream
  [07/12]: remote.c: add branch_get_push
  [08/12]: sha1_name: refactor upstream_mark
  [09/12]: sha1_name: refactor interpret_upstream_mark
  [10/12]: sha1_name: implement @{push} shorthand
  [11/12]: for-each-ref: use skip_prefix instead of starts_with
  [12/12]: for-each-ref: accept "%(push)" format

-Peff

             reply	other threads:[~2015-05-01 22:44 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-01 22:44 Jeff King [this message]
2015-05-01 22:44 ` [PATCH 01/12] remote.c: drop default_remote_name variable Jeff King
2015-05-01 22:45 ` [PATCH 02/12] remote.c: drop "remote" pointer from "struct branch" Jeff King
2015-05-03  3:34   ` Eric Sunshine
2015-05-05 19:31     ` Jeff King
2015-05-07  9:33       ` Jeff King
2015-05-01 22:45 ` [PATCH 03/12] remote.c: hoist branch.*.remote lookup out of remote_get_1 Jeff King
2015-05-01 22:46 ` [PATCH 04/12] remote.c: provide per-branch pushremote name Jeff King
2015-05-03  4:51   ` Eric Sunshine
2015-05-05 19:33     ` Jeff King
2015-05-05 19:48       ` Eric Sunshine
2015-05-07  9:38         ` Jeff King
2015-05-08 16:13           ` Eric Sunshine
2015-05-01 22:47 ` [PATCH 05/12] remote.c: introduce branch_get_upstream helper Jeff King
2015-05-01 22:52 ` [PATCH 06/12] remote.c: report specific errors from branch_get_upstream Jeff King
2015-05-01 22:53 ` [PATCH 07/12] remote.c: add branch_get_push Jeff King
2015-05-01 22:53 ` [PATCH 08/12] sha1_name: refactor upstream_mark Jeff King
2015-05-01 22:55 ` [PATCH 09/12] sha1_name: refactor interpret_upstream_mark Jeff King
2015-05-01 22:55 ` [PATCH 10/12] sha1_name: implement @{push} shorthand Jeff King
2015-05-01 22:55 ` [PATCH 11/12] for-each-ref: use skip_prefix instead of starts_with Jeff King
2015-05-01 22:56 ` [PATCH 12/12] for-each-ref: accept "%(push)" format Jeff King

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=20150501224414.GA25551@peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.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.
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).