git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Karthik Nayak <karthik.188@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, christian.couder@gmail.com,
	Matthieu.Moy@grenoble-inp.fr
Subject: Re: [RFC/PATCH 1/9] tag: libify parse_opt_points_at()
Date: Tue, 09 Jun 2015 17:20:55 +0530	[thread overview]
Message-ID: <5576D31F.90603@gmail.com> (raw)
In-Reply-To: <xmqq4mmiauu0.fsf@gitster.dls.corp.google.com>

On 06/09/2015 12:30 AM, Junio C Hamano wrote:
>
> This feels way too specialized to live as part of parse_options
> infrastructure.
>
> The existing caller(s) may want to use this callback for parsing
> "points-at" option they have, but is that the only plausible use of
> this callback?  It looks to be usable by any future caller that
> wants to take and accumulate any object names into an sha1-array, so
> perhaps rename it to be a bit more generic to represent its nature
> better?
>
> 	parse_opt_object_name()
>
> or something?

This makes sense! Will change.

>
> I also wonder if we can (and want to) refactor the users of
> with-commit callback.  Have them use this to obtain an sha1-array
> and then convert what they received into a commit-list themselves.
>

But wouldn't that be too much of an overhead to iterate through the
sha1-array and convert it to a commit-list?

-- 
Regards,
Karthik

  reply	other threads:[~2015-06-09 11:51 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-06 20:03 [RFC/PATCH 0/9] add options to ref-filter Karthik Nayak
2015-06-06 20:04 ` [RFC/PATCH 1/9] tag: libify parse_opt_points_at() Karthik Nayak
2015-06-06 20:04   ` [RFC/PATCH 2/9] ref-filter: implement '--points-at' option Karthik Nayak
2015-06-08 17:31     ` Matthieu Moy
2015-06-08 18:50       ` Karthik Nayak
2015-06-08 18:00     ` Matthieu Moy
2015-06-08 18:54       ` Karthik Nayak
2015-06-06 20:04   ` [RFC/PATCH 3/9] for-each-ref: add " Karthik Nayak
2015-06-08 17:35     ` Matthieu Moy
2015-06-08 18:51       ` Karthik Nayak
2015-06-08 19:12     ` Junio C Hamano
2015-06-09 12:01       ` Karthik Nayak
2015-06-09 19:07         ` Junio C Hamano
2015-06-10  6:55           ` Karthik Nayak
2015-06-10  7:39           ` Matthieu Moy
2015-06-10 11:31             ` Karthik Nayak
2015-06-06 20:04   ` [RFC/PATCH 4/9] parse-options: add parse_opt_merge_filter() Karthik Nayak
2015-06-08 17:58     ` Matthieu Moy
2015-06-08 18:54       ` Karthik Nayak
2015-06-08 19:20     ` Junio C Hamano
2015-06-09 12:36       ` Karthik Nayak
2015-06-06 20:04   ` [RFC/PATCH 5/9] ref-filter: implement '--merged' and '--no-merged' options Karthik Nayak
2015-06-08 17:51     ` Matthieu Moy
2015-06-08 18:53       ` Karthik Nayak
2015-06-06 20:04   ` [RFC/PATCH 6/9] for-each-ref: add " Karthik Nayak
2015-06-08 17:53     ` Matthieu Moy
2015-06-08 18:54       ` Karthik Nayak
2015-06-06 20:04   ` [RFC/PATCH 7/9] parse-options.h: add macros for '--contains' option Karthik Nayak
2015-06-08 19:32     ` Junio C Hamano
2015-06-09 12:49       ` Karthik Nayak
2015-06-06 20:04   ` [RFC/PATCH 8/9] ref-filter: add " Karthik Nayak
2015-06-06 20:04   ` [RFC/PATCH 9/9] for-each-ref: " Karthik Nayak
2015-06-08 19:00   ` [RFC/PATCH 1/9] tag: libify parse_opt_points_at() Junio C Hamano
2015-06-09 11:50     ` Karthik Nayak [this message]
2015-06-07 13:10 ` [RFC/PATCH 0/9] add options to ref-filter Christian Couder
2015-06-08 15:00   ` Karthik Nayak
2015-06-08 19:34 ` 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=5576D31F.90603@gmail.com \
    --to=karthik.188@gmail.com \
    --cc=Matthieu.Moy@grenoble-inp.fr \
    --cc=christian.couder@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).