From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 7/7] sha1_name: implement finding @{push}
Date: Thu, 23 May 2013 20:42:50 +0530 [thread overview]
Message-ID: <1369321970-7759-8-git-send-email-artagnon@gmail.com> (raw)
In-Reply-To: <1369321970-7759-1-git-send-email-artagnon@gmail.com>
Try this now: configure your current branch's pushremote to push to
"refs/heads/*:refs/heads/rr/*". Now, type 'git show @{p}'. Voila!
It currently only works when:
1. remote.<name>.push is explicitly specified.
2. There is a pattern to match (*).
Proof-of-concept only.
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
sha1_name.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/sha1_name.c b/sha1_name.c
index 5f6958b..283d538 100644
--- a/sha1_name.c
+++ b/sha1_name.c
@@ -1008,6 +1008,24 @@ static void die_no_upstream(struct branch *upstream, char *name) {
}
}
+static void find_push_ref(struct branch *branch) {
+ struct remote *remote = pushremote_get(NULL);
+ const struct refspec *pat = NULL;
+ char raw_ref[PATH_MAX];
+ struct ref *this_ref;
+ char *dst_name;
+ int len;
+
+ sprintf(raw_ref, "refs/heads/%s", branch->name);
+ len = strlen(raw_ref) + 1;
+ this_ref = xcalloc(1, sizeof(*this_ref) + len);
+ memcpy(this_ref->name, raw_ref, len);
+
+ dst_name = get_ref_match(remote->push, remote->push_refspec_nr,
+ this_ref, MATCH_REFS_ALL, 0, &pat);
+ printf("dst_name = %s\n", dst_name);
+}
+
/*
* This reads short-hand syntax that not only evaluates to a commit
* object name, but also can act as if the end user spelled the name
@@ -1085,6 +1103,8 @@ int interpret_branch_name(const char *name, struct strbuf *buf)
cp = shorten_unambiguous_ref(branch->merge[0]->dst, 0);
break;
case AT_KIND_PUSH:
+ find_push_ref(branch);
+ die("Done!");
break;
}
--
1.8.3.rc3.17.gd95ec6c.dirty
next prev parent reply other threads:[~2013-05-23 15:11 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-23 15:12 [PATCH 0/7] Let's get that @{push}! Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 1/7] sha1_name: abstract upstream_mark() logic Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 2/7] sha1_name: factor out die_no_upstream() Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 3/7] sha1_name: remove upstream_mark() Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 4/7] remote: expose parse_push_refspec() Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 5/7] remote: expose get_ref_match() Ramkumar Ramachandra
2013-05-23 15:12 ` [PATCH 6/7] sha1_name: prepare to introduce AT_KIND_PUSH Ramkumar Ramachandra
2013-05-24 13:22 ` Felipe Contreras
2013-05-24 13:27 ` Ramkumar Ramachandra
2013-05-23 15:12 ` Ramkumar Ramachandra [this message]
2013-05-24 16:09 ` [PATCH 7/7] sha1_name: implement finding @{push} Duy Nguyen
2013-05-24 16:15 ` Ramkumar Ramachandra
2013-05-24 16:21 ` Duy Nguyen
2013-05-24 16:29 ` Ramkumar Ramachandra
2013-05-24 18:01 ` Junio C Hamano
2013-05-24 18:21 ` Ramkumar Ramachandra
2013-05-24 19:12 ` 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=1369321970-7759-8-git-send-email-artagnon@gmail.com \
--to=artagnon@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).