From: Jakub Narebski <jnareb@gmail•com>
To: git@vger•kernel.org
Subject: Re: [PATCH] git-status: wording update to deal with deleted files.
Date: Fri, 12 Jan 2007 20:48:34 +0100 [thread overview]
Message-ID: <eo8ols$ja$2@sea.gmane.org> (raw)
In-Reply-To: 878xg9xcca.wl%cworth@cworth.org
Carl Worth wrote:
> commit after stage
> ------------------
> git stage: stage content for new, modified, or removed files
>
> commit -a
> ---------
> git add: mark new files to be committed
>
> Compare that to the above description. Isn't it beautiful from a
> conceptual point-of-view? The "git rm" command isn't needed at all,
> (though we could certainly still provide it). And now the "git add"
> command only has one conceptual use, for (of all thing!) adding new
> files, not updating content for files that have been modified.
Without "git rm" (or "git update-index --force-remove") you cannot
make file to be untracked by git, i.e. remove it from the files
tracked by git but not remove it from directory.
With current version of git-rm (modulo bugs), if you do "git rm <file>"
the file would be removed from index, and if recoverable from working
directory. Without git-rm you would have to use plumbing to remove it from
index but preserve changes.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-01-12 19:48 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 [this message]
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
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='eo8ols$ja$2@sea.gmane.org' \
--to=jnareb@gmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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