git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Stephan Beyer <s-beyer@gmx.net>
Cc: git@vger.kernel.org, gitster@pobox.com,
	Daniel Barkalow <barkalow@iabervon.org>,
	Christian Couder <chriscool@tuxfamily.org>,
	Alex Riesen <raa.lkml@gmail.com>, Jeff King <peff@peff.net>
Subject: Re: [PATCH] Generalize and libify index_is_dirty() to index_differs_from(...)
Date: Mon, 09 Feb 2009 21:16:23 -0800	[thread overview]
Message-ID: <7v63jirhw8.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <1234222843-15577-1-git-send-email-s-beyer@gmx.net> (Stephan Beyer's message of "Tue, 10 Feb 2009 00:40:43 +0100")

Stephan Beyer <s-beyer@gmx.net> writes:

>   This is one of the sequencer-preparing patches.
>   (The function is used in sequencer several times, most of the time
>    with diff_flags set to DIFF_OPT_IGNORE_SUBMODULES.)
>
>   Alex is on Cc because he introduced the "Is commitable?" (i.e.
>   "Is index dirty?") part in builtin-commit.c.
>
>   Peff is on Cc because he introduced index_is_dirty() in
>   builtin-revert.c.
>
>  builtin-commit.c |   13 ++-----------
>  builtin-revert.c |   13 +------------
>  revision.c       |   15 +++++++++++++++
>  revision.h       |    2 ++
>  4 files changed, 20 insertions(+), 23 deletions(-)

It is a straightforward and clean restructuring, but please do not
contaminate revision.[ch] with this function about "internally running
diff-index".  

revision.[ch] is a library for revision/ancestry traversal and it is
already one of the largest library-ish files. It does not know nor care
about the index, and we want to keep it that way.  Please keep its focus
to revision traversal.

Perhaps diff-lib.c would be a better home for your helper function.

  parent reply	other threads:[~2009-02-10  5:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-09 23:40 [PATCH] Generalize and libify index_is_dirty() to index_differs_from(...) Stephan Beyer
2009-02-10  0:12 ` Jeff King
2009-02-10  5:16 ` Junio C Hamano [this message]
2009-02-10 14:30   ` [PATCH v2] " Stephan Beyer

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=7v63jirhw8.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=barkalow@iabervon.org \
    --cc=chriscool@tuxfamily.org \
    --cc=git@vger.kernel.org \
    --cc=peff@peff.net \
    --cc=raa.lkml@gmail.com \
    --cc=s-beyer@gmx.net \
    /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).