From: Miklos Vajna <vmiklos@frugalware.org>
To: Eric Raible <raible@gmail.com>
Cc: Jeff Whiteside <jeff.m.whiteside@gmail.com>,
Elijah Newren <newren@gmail.com>,
Changsheng Jiang <jiangzuoyan@gmail.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: RFC: perhaps a "new file" should not be deleted by "git reset --hard"
Date: Fri, 12 Sep 2008 17:41:26 +0200 [thread overview]
Message-ID: <20080912154126.GW4829@genesis.frugalware.org> (raw)
In-Reply-To: <279b37b20809111649h77666a46u362dddfa1b40e0ca@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 344 bytes --]
On Thu, Sep 11, 2008 at 04:49:54PM -0700, Eric Raible <raible@gmail.com> wrote:
> What advantages does "git read-tree -m HEAD" have over "git reset" or
> "git rm --cached <file list>"?
Nothing. I should stop advertising that I still use a lot of plumbing
when a porcelain like 'git reset' does the job as well. ;-(
Thanks for the correction.
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2008-09-12 15:42 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-10 19:12 RFC: perhaps a "new file" should not be deleted by "git reset --hard" Eric Raible
[not found] ` <eafc0afe0809101912v72916d3hce9ae5d6812f0db8@mail.gmail.com>
2008-09-11 2:14 ` Changsheng Jiang
2008-09-11 2:38 ` Elijah Newren
2008-09-11 20:50 ` Eric Raible
2008-09-11 21:34 ` Junio C Hamano
2008-09-11 22:19 ` Eric Raible
2008-09-11 23:04 ` Jeff Whiteside
2008-09-11 23:29 ` Eric Raible
2008-09-11 2:46 ` Eric Raible
2008-09-11 6:05 ` Changsheng Jiang
2008-09-11 6:15 ` RFC: perhaps a Eric Raible
2008-09-11 16:32 ` RFC: perhaps a "new file" should not be deleted by "git reset --hard" Elijah Newren
[not found] ` <3ab397d0809111022m24c81bd9y2520f6be478babd3@mail.gmail.com>
2008-09-11 21:24 ` Eric Raible
2008-09-11 23:39 ` Miklos Vajna
2008-09-11 23:49 ` Eric Raible
2008-09-12 15:41 ` Miklos Vajna [this message]
2008-09-11 6:14 ` Mike Hommey
2008-09-11 20:26 ` Eric Raible
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=20080912154126.GW4829@genesis.frugalware.org \
--to=vmiklos@frugalware.org \
--cc=git@vger.kernel.org \
--cc=jeff.m.whiteside@gmail.com \
--cc=jiangzuoyan@gmail.com \
--cc=newren@gmail.com \
--cc=raible@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.