Let's start off from where the previous discussion [1] stopped. People
seem to agree ref^{/regex} is a good choice. But we have not come to
conclusion how to specify the count yet. Possible suggestions are
- ref^{/foo}2
- ref^{2/foo}
- ref^{:2/foo}
- ref^{2nd/foo}
For whatever syntax chosen, :/ should benefit too. I notice that :/!
is reserved for future use. Perhaps :/!2/regex is not too cryptic?
I'd also like to do case-insensitive regex, by the way. :/!2i/regex
looks a bit ugly.
[1] http://mid.gmane.org/9D675671-693D-4B59-AF2A-0EFE4C537362@xxxxxx
Nguyán ThÃi Ngác Duy (2):
get_sha1_oneline: allow to input commit_list
get_sha1: support ref^{/regex} syntax
Documentation/revisions.txt | 7 ++++++
sha1_name.c | 45 ++++++++++++++++++++++++++++++++----------
2 files changed, 41 insertions(+), 11 deletions(-)
--
1.7.3.2.316.gda8b3
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html