From: Junio C Hamano <gitster@pobox•com>
To: Kevin Daudt <me@ikke•info>
Cc: Sidhant Sharma <tigerkid001@gmail•com>,
Lars Schneider <larsxschneider@gmail•com>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: [RFC/GSoC] Introduction
Date: Mon, 14 Mar 2016 00:01:07 -0700 [thread overview]
Message-ID: <xmqqfuvt8rws.fsf@gitster.mtv.corp.google.com> (raw)
In-Reply-To: <20160313211910.GA22052@ikke.info> (Kevin Daudt's message of "Sun, 13 Mar 2016 22:19:10 +0100")
Kevin Daudt <me@ikke•info> writes:
> On Mon, Mar 14, 2016 at 12:03:33AM +0530, Sidhant Sharma wrote:
>>
>>
>>
>> Other than this, I also tried to expand the list of potentially destructive
>> commands and updated the list as follows (additions in brackets):
>>
>> * git rebase [ git pull --rebase ]
>> * git reset --hard
>> * git clean -f
>> * git gc --prune=now --aggressive
>> * git push -f [ git push <remote> :<branch>, git push <remote> +<branch> ]
>> * [ git branch -D ]
>>
>> Are these additions appropriate? What other commands should be included?
>
> git checkout [ref] <file> is destructive too if it would overwrite an
> uncomitted change.
Obviously. As that was designed to be the way to get rid of
unsuccessful/unwanted edit in the working tree.
"git add <file>" is destructive if it overwrites the index entry
that holds contents you have not committed.
"git rm [--cached] <file>" is destructive, too.
I think "git checkout [<ref>] <file>" falls into the same category.
next prev parent reply other threads:[~2016-03-14 7:01 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-12 6:59 [RFC/GSoC] Introduction Sidhant Sharma
2016-03-13 15:50 ` Lars Schneider
2016-03-13 18:33 ` Sidhant Sharma
2016-03-13 21:19 ` Kevin Daudt
2016-03-14 5:25 ` Sidhant Sharma
2016-03-14 6:15 ` Jacob Keller
2016-03-14 7:01 ` Junio C Hamano [this message]
2016-03-13 23:28 ` Jacob Keller
2016-03-14 5:25 ` Sidhant Sharma
2016-03-14 6:14 ` Jacob Keller
2016-03-14 16:00 ` Sidhant Sharma
2016-03-14 6:57 ` Junio C Hamano
2016-03-14 8:16 ` Lars Schneider
2016-03-14 15:56 ` Sidhant Sharma
2016-03-20 20:17 ` Matthieu Moy
2016-03-14 17:25 ` Junio C Hamano
2016-03-20 20:28 ` Matthieu Moy
2016-03-14 21:08 ` Philip Oakley
2016-03-17 14:52 ` Sidhant Sharma
2016-03-20 15:39 ` Lars Schneider
2016-03-20 15:51 ` Sidhant Sharma
2016-03-20 16:08 ` Lars Schneider
2016-03-20 16:22 ` Sidhant Sharma
-- strict thread matches above, loose matches on Subject: below --
2016-03-22 17:51 Philip Oakley
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=xmqqfuvt8rws.fsf@gitster.mtv.corp.google.com \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=larsxschneider@gmail$(echo .)com \
--cc=me@ikke$(echo .)info \
--cc=tigerkid001@gmail$(echo .)com \
/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