From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH 1/2] sha1_name: fix error message for @{u}
Date: Wed, 22 May 2013 00:49:47 +0530 [thread overview]
Message-ID: <CALkWK0m7VBz3wDGUACJAfp33M1GYqKCeMCkQwrgA7kqRMp_rtQ@mail.gmail.com> (raw)
In-Reply-To: <CALkWK0nEXKXxercc1mNjyK-QX0pOBeKWAxPZtSPvN_h1eniO5g@mail.gmail.com>
Ramkumar Ramachandra wrote:
> Junio C Hamano wrote:
>> So did you or did you not audit the codepath?
>
> No; I was explaining why I didn't in the first place. Going through it now.
So, this is what I have:
interpret_branch_name -> interpret_branch_name (recursion)
-> get_sha1_basic -> get_sha1 [context] (end-user data)
-> substitute_branch_name -> dwim (end-user data)
-> strbuf_branchname (callers pass a branch name; no @{u})
-> revision.c:add_pending_object [with_mode] (end-user data)
[die_]verify_filename -> builtin/rev-parse.c (end-user)
-> builtin/reset.c (end-user)
-> builtin/grep.c:cmd_grep (end-user)
-> revision.c:setup_revisions (end-user data)
We used to die in die_verify_filename() earlier, but we die in
interpret_branch_name() after the patch. Do we have to dig deeper?
next prev parent reply other threads:[~2013-05-21 19:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-21 10:41 [PATCH 0/2] Fix invalid revision error messages for 1.8.3 Ramkumar Ramachandra
2013-05-21 10:41 ` [PATCH 1/2] sha1_name: fix error message for @{u} Ramkumar Ramachandra
2013-05-21 16:42 ` Junio C Hamano
2013-05-21 17:56 ` Ramkumar Ramachandra
2013-05-21 18:02 ` Junio C Hamano
2013-05-21 18:04 ` Ramkumar Ramachandra
2013-05-21 18:09 ` Junio C Hamano
2013-05-21 19:19 ` Ramkumar Ramachandra [this message]
2013-05-21 20:08 ` Junio C Hamano
2013-05-21 20:14 ` Ramkumar Ramachandra
2013-05-21 20:33 ` Junio C Hamano
2013-05-21 10:41 ` [PATCH 2/2] sha1_name: fix error message for @{<N>}, @{<date>} Ramkumar Ramachandra
2013-05-21 16:52 ` Junio C Hamano
2013-05-21 17:38 ` Kevin Bracey
2013-05-21 18:09 ` Ramkumar Ramachandra
2013-05-21 16:36 ` [PATCH 0/2] Fix invalid revision error messages for 1.8.3 Junio C Hamano
2013-05-21 17:50 ` Ramkumar Ramachandra
2013-05-21 17:57 ` Junio C Hamano
2013-05-21 18:16 ` Ramkumar Ramachandra
-- strict thread matches above, loose matches on Subject: below --
2013-05-22 10:39 [PATCH v2 0/2] Fix invalid revision error messages Ramkumar Ramachandra
2013-05-22 10:39 ` [PATCH 1/2] sha1_name: fix error message for @{u} Ramkumar Ramachandra
2013-05-22 17:35 ` Junio C Hamano
2013-05-23 11:03 ` Ramkumar Ramachandra
2013-05-24 7:42 [PATCH v3 0/2] Replacement for rr/die-on-missing-upstream Ramkumar Ramachandra
2013-05-24 7:42 ` [PATCH 1/2] sha1_name: fix error message for @{u} Ramkumar Ramachandra
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=CALkWK0m7VBz3wDGUACJAfp33M1GYqKCeMCkQwrgA7kqRMp_rtQ@mail.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).