From: Marko Macek <marko.macek@gmx.net>
To: git@vger.kernel.org
Subject: Re: [RFC] Introduce "git stage" (along with some heresy)
Date: Fri, 01 Dec 2006 21:44:28 +0100 [thread overview]
Message-ID: <4570942C.406@gmx.net> (raw)
In-Reply-To: <87slfzfri7.wl%cworth@cworth.org>
Carl Worth wrote:
> [This message, (yes,another long one from me), proposes 3 changes. The
> first should be uncontroversial I think, while the second and third
> are clear heresy, (and the second would require some amount of
> re-training or re-configuration by existing git user). Pick and choose
> as you see fit. I don't think they actually depend on each other,
> though I'll present them here as parts of a whole.]
/me likes (both emails).
Q: should git-commit require either -a or --staged when there is a
staged commit?
Mark
next prev parent reply other threads:[~2006-12-01 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-01 17:36 [RFC] Introduce "git stage" (along with some heresy) Carl Worth
2006-12-01 20:03 ` Some thoughts on resolving conflicts Carl Worth
2006-12-01 20:44 ` Marko Macek [this message]
2006-12-02 21:03 ` [RFC] Introduce "git stage" (along with some heresy) Sam Vilain
2006-12-02 22:33 ` Wink Saville
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=4570942C.406@gmx.net \
--to=marko.macek@gmx.net \
--cc=git@vger.kernel.org \
/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).