From: Jeff King <peff@peff.net>
To: Carl Worth <cworth@cworth.org>
Cc: git@vger.kernel.org
Subject: Re: Removing files
Date: Thu, 11 Jan 2007 19:17:55 -0500 [thread overview]
Message-ID: <20070112001754.GD16042@coredump.intra.peff.net> (raw)
In-Reply-To: <87bql5xhbi.wl%cworth@cworth.org>
On Thu, Jan 11, 2007 at 03:41:05PM -0800, Carl Worth wrote:
> git commit -a
>
> Commit the working-tree content of all files known to git.
>
> git commit paths...
>
> Commit changes from the working-tree content of the specified
> paths.
>
> git commit
>
> Commit changes from all content that has been staged with
> "git stage".
>
[...]
> I really like the simplicity of explanation that this model
> provides. And I'd love to hear any feedback that anybody has about it.
I think this is a very easy way of explaining it in the documentation.
But what do you think 'git status' should say about changed files?
Currently we make recommendations about how to stage the various files.
It would certainly be simpler to recommend 'git commit -a' for changes,
but that feels wrong.
-Peff
prev parent reply other threads:[~2007-01-12 0:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-11 20:10 Removing files David Kågedal
2007-01-11 21:36 ` Alex Riesen
2007-01-11 22:25 ` Seth Falcon
2007-01-11 22:41 ` Junio C Hamano
2007-01-11 23:19 ` Eric Wong
2007-01-11 23:36 ` Junio C Hamano
2007-01-11 23:37 ` [PATCH] git-status: wording update to deal with deleted files Junio C Hamano
2007-01-11 23:56 ` Carl Worth
2007-01-12 0:13 ` Junio C Hamano
2007-01-12 1:28 ` Carl Worth
2007-01-12 19:48 ` Jakub Narebski
2007-01-12 0:07 ` Jeff King
2007-01-12 22:13 ` Juergen Ruehle
2007-01-11 23:41 ` Removing files Carl Worth
2007-01-12 0:17 ` Jeff King [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=20070112001754.GD16042@coredump.intra.peff.net \
--to=peff@peff.net \
--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).