All of lore.kernel.org
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Marco Costalba <mcostalba@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] git-commit: revamp the git-commit semantics.
Date: Sun, 05 Feb 2006 12:03:45 -0800	[thread overview]
Message-ID: <7v64ntindq.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <e5bfff550602050536j73f1091dq9afae232f574d0b4@mail.gmail.com> (Marco Costalba's message of "Sun, 5 Feb 2006 14:36:51 +0100")

I was planning to think about the migration strategy _after_ I
get the feeling that everybody who got confused by the current
one thinks this is a good change, and I am glad you did that
work for me ;-).

I think it is sane to add a no-op '--include' to the current
version.

I am not sure if it is worth to take two-phased introduction of
this new "temporary index" thing.  We could:

 * add '--only' that asks for the new "temporary index" thing.

 * initially make '--include' the default, not '--only'.

 * later switch the default to '--only'.

  reply	other threads:[~2006-02-05 20:03 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-05 10:24 [PATCH] git-commit: revamp the git-commit semantics Junio C Hamano
2006-02-05 13:36 ` Marco Costalba
2006-02-05 20:03   ` Junio C Hamano [this message]
2006-02-05 22:08     ` Marco Costalba
2006-02-05 23:10       ` Junio C Hamano
2006-02-07 16:59         ` Nicolas Pitre
2006-02-07 17:50           ` Junio C Hamano
2006-02-07 18:18             ` Junio C Hamano
2006-02-07 19:25               ` Jon Loeliger
2006-02-07 18:39             ` Nicolas Pitre
2006-02-07 19:18               ` Nicolas Pitre
2006-02-08  5:41                 ` Junio C Hamano
     [not found] ` <20060205225116.GC24561@blinkenlights.visv.net>
2006-02-06  0:03   ` Junio C Hamano
2006-02-06  1:32     ` Junio C Hamano
2006-02-06  2:25       ` Michael Fischer
2006-02-06  7:31         ` 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=7v64ntindq.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=git@vger.kernel.org \
    --cc=mcostalba@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.