From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Sam Ravnborg" <sam@ravnborg.org>
Cc: git@vger.kernel.org
Subject: Re: git reset --hard include/linux/config.h
Date: Wed, 5 Jul 2006 19:29:07 +0200 [thread overview]
Message-ID: <81b0412b0607051029q175928faq113b81de8c11db30@mail.gmail.com> (raw)
In-Reply-To: <20060705171406.GA17834@mars.ravnborg.org>
On 7/5/06, Sam Ravnborg <sam@ravnborg.org> wrote:
> On Wed, Jul 05, 2006 at 07:05:27PM +0200, Alex Riesen wrote:
> > On 7/5/06, Sam Ravnborg <sam@ravnborg.org> wrote:
> > >Also what is the right command to bring back a file to the original
> > >state after doing some modifications that was not needed anyway?
> >
> > git checkout HEAD include/linux/config.h
>
> Thanks!
>
> By the way - the modifications to include/linux/config.h was not lost.
> But git apperantly managed to be fooled to think the file was
> up-to-date.
After that checkout or after reset --hard? Both is quiet unusual, though
next prev parent reply other threads:[~2006-07-05 17:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-05 16:58 git reset --hard include/linux/config.h Sam Ravnborg
2006-07-05 17:05 ` Alex Riesen
2006-07-05 17:14 ` Sam Ravnborg
2006-07-05 17:29 ` Alex Riesen [this message]
2006-07-06 2:45 ` Junio C Hamano
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=81b0412b0607051029q175928faq113b81de8c11db30@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=git@vger.kernel.org \
--cc=sam@ravnborg.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).