git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: purserj@winnsw.com.au
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Adding Correct Useage Notification and -h Help flag
Date: Mon, 13 Jun 2005 22:52:25 -0700	[thread overview]
Message-ID: <7vaclt8oyu.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <1118726714.8712.22.camel@localhost.localdomain> (James Purser's message of "Tue, 14 Jun 2005 15:25:14 +1000")

>>>>> "JP" == James Purser <purserj@winnsw.com.au> writes:

JP> When running git commit I am told to run git-update-cache
JP> against the files I want to commit. Would it be easier to
JP> have the git-commit-script run this itself? Take out that
JP> second step and all that.

That's a question better asked Linus, not me.  My preference
would be (1) to ask the user if he wants us to automatically run
git-update-cache to all of those files, giving him an option to
decline and sort things out himself; or (2) leave things as they
are.

The core GIT treats the index file and the working directory
contents two logically separate entities, and we always require
the user to consciously tell us what to put in and remove from
the index file.  The core GIT is all about committed tree
objects and the index file, and the working directory is merely
a temporary area the user can use to build the state the user
wishes to have in the index file.  From this point of view,
running git-update-cache ourselves without asking the user is a
definite no-no.


  reply	other threads:[~2005-06-14  5:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-14  1:47 [PATCH] Adding Correct Useage Notification and -h Help flag James Purser
2005-06-14  2:23 ` Junio C Hamano
2005-06-14  2:28   ` James Purser
2005-06-14  5:25   ` James Purser
2005-06-14  5:52     ` Junio C Hamano [this message]
2005-06-14 21:49   ` James Purser

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7vaclt8oyu.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=purserj@winnsw.com.au \
    /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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).