From: Wink Saville <wink@saville.com>
To: Carl Worth <cworth@cworth.org>
Cc: git@vger.kernel.org
Subject: Re: [RFC] Introduce "git stage" (along with some heresy)
Date: Sat, 02 Dec 2006 14:33:34 -0800 [thread overview]
Message-ID: <4571FF3E.4090209@saville.com> (raw)
In-Reply-To: <87slfzfri7.wl%cworth@cworth.org>
Carl Worth wrote:
>
> Without staging
> ---------------
> add Add a file to be managed by git
>
> rm Remove a file to no longer be managed by git
>
> diff Show the changes in the working tree compared to the
> latest commit, (or compared to staged content, if any)
>
> commit Commit the current state of all git-managed files
>
> commit files... Commit the current state of the specified files
>
As a newbie like this entire proposal and especially the above.
Wink Saville
prev parent reply other threads:[~2006-12-02 22:33 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 ` [RFC] Introduce "git stage" (along with some heresy) Marko Macek
2006-12-02 21:03 ` Sam Vilain
2006-12-02 22:33 ` Wink Saville [this message]
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=4571FF3E.4090209@saville.com \
--to=wink@saville.com \
--cc=cworth@cworth.org \
--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).