From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Git List <git@vger.kernel.org>
Cc: Junio C Hamano <gitster@pobox.com>
Subject: [PATCH 1/7] sha1_name: abstract upstream_mark() logic
Date: Thu, 23 May 2013 20:42:44 +0530 [thread overview]
Message-ID: <1369321970-7759-2-git-send-email-artagnon@gmail.com> (raw)
In-Reply-To: <1369321970-7759-1-git-send-email-artagnon@gmail.com>
Currently, the only non-numerical @{...} expression we support is
@{u[pstream]}. Since we're slowly growing git to support triangular
workflows, it might make sense to have a @{p[ush]} and various other
special @{...} expressions in the future. To prepare for this, abstract
out the upstream_mark() logic to accept any suffix, while preserving the
upstream_mark() interface.
Signed-off-by: Ramkumar Ramachandra <artagnon@gmail.com>
---
sha1_name.c | 40 +++++++++++++++++++++++++++++++---------
1 file changed, 31 insertions(+), 9 deletions(-)
diff --git a/sha1_name.c b/sha1_name.c
index 6928cc7..766e4e9 100644
--- a/sha1_name.c
+++ b/sha1_name.c
@@ -23,6 +23,8 @@ struct disambiguate_state {
unsigned always_call_fn:1;
};
+#define AT_KIND_UPSTREAM 0
+
static void update_candidates(struct disambiguate_state *ds, const unsigned char *current)
{
if (ds->always_call_fn) {
@@ -416,20 +418,40 @@ static int ambiguous_path(const char *path, int len)
return slash;
}
-static inline int upstream_mark(const char *string, int len)
+static inline int at_mark(const char *string, int len, int *kind)
{
- const char *suffix[] = { "@{upstream}", "@{u}" };
- int i;
-
- for (i = 0; i < ARRAY_SIZE(suffix); i++) {
- int suffix_len = strlen(suffix[i]);
- if (suffix_len <= len
- && !memcmp(string, suffix[i], suffix_len))
- return suffix_len;
+ int i, j;
+
+ static struct {
+ int kind;
+ const char *suffix[2];
+ } at_form[] = {
+ { AT_KIND_UPSTREAM, { "@{upstream}", "@{u}" } }
+ };
+
+ for (j = 0; j < ARRAY_SIZE(at_form); j++) {
+ for (i = 0; i < ARRAY_SIZE(at_form[j].suffix); i++) {
+ int suffix_len = strlen(at_form[j].suffix[i]);
+ if (suffix_len <= len
+ && !memcmp(string, at_form[j].suffix[i], suffix_len)) {
+ if (kind)
+ *kind = at_form[j].kind;
+ return suffix_len;
+ }
+ }
}
return 0;
}
+static inline int upstream_mark(const char *string, int len)
+{
+ int suffix_len, kind;
+ suffix_len = at_mark(string, len, &kind);
+ if (suffix_len && kind == AT_KIND_UPSTREAM)
+ return suffix_len;
+ return 0;
+}
+
static int get_sha1_1(const char *name, int len, unsigned char *sha1, unsigned lookup_flags);
static int get_sha1_basic(const char *str, int len, unsigned char *sha1)
--
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 ` Ramkumar Ramachandra [this message]
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 ` [PATCH 7/7] sha1_name: implement finding @{push} Ramkumar Ramachandra
2013-05-24 16:09 ` 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-2-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).