Thread (4 messages) flat view 4 messages, 3 authors, 2016-06-15

RE: three questions: proper forum? & reverting changes to the working directory

From: McKown, John <hidden>
Date: 2016-06-15 22:55:12

Well, a message I read after posting seems to have answered question #3. I'll look at "git checkout", which ignorant me thought was only used to change branches.

-- 
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mckown@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or proprietary information. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message. HealthMarkets(r) is the brand name for products underwritten and issued by the insurance subsidiaries of HealthMarkets, Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life Insurance Company of TennesseeSM and The MEGA Life and Health Insurance Company.SM

-----Original Message-----
From: git-owner@vger.kernel.org [mailto:git-owner@vger.kernel.org] On
Behalf Of McKown, John
Sent: Thursday, November 08, 2012 8:26 AM
To: 'git@vger.kernel.org'
Subject: three questions: proper forum? & reverting changes to the
working directory

1) is this the proper forum for asking general git usage questions,
such as "how to"? If not, what is?

2) I am unsure that I did things the "proper" way. I have a git
maintained subdirectory. I made some changes and saved them in the
working directory, but did not "git add" or "git commit" them. I then
decided that I really messed up what I was doing (basically
reformatting some source code). So to revert the changes back to what
was last committed, I did a "git reset --hard HEAD". I think this is
the proper way. But I picked up that command in the section of the
documentation which was talking about abandoning a "git merge" attempt.
What I did worked, but is it the proper way? If not, what is?

3) More generically, suppose I have a file in my working directory that
I want to put back the way it was "n" commits ago. The best that I can
see, so far, is "git show HEAD~n:file >|file", replacing the "n" and
"file" with appropriate values.

--
John McKown
Systems Engineer IV
IT

Administrative Services Group

HealthMarkets(r)

9151 Boulevard 26 * N. Richland Hills * TX 76010
(817) 255-3225 phone *
john.mckown@healthmarkets.com * www.HealthMarkets.com

Confidentiality Notice: This e-mail message may contain confidential or
proprietary information. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the
original message. HealthMarkets(r) is the brand name for products
underwritten and issued by the insurance subsidiaries of HealthMarkets,
Inc. -The Chesapeake Life Insurance Company(r), Mid-West National Life
Insurance Company of TennesseeSM and The MEGA Life and Health Insurance
Company.SM


--
To unsubscribe from this list: send the line "unsubscribe git" in the
body of a message to majordomo@vger.kernel.org More majordomo info at
http://vger.kernel.org/majordomo-info.html
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help