From: David Kastrup <dak@gnu.org>
To: "Nikodemus Siivola" <nikodemus@random-state.net>
Cc: "Shawn O. Pearce" <spearce@spearce.org>,
"Jan Hudec" <bulb@ucw.cz>,
"Brian Scott Dobrovodsky" <brian@pontech.com>,
git@vger.kernel.org
Subject: Re: Data Integrity & un-Commited Branches
Date: Sat, 15 Sep 2007 19:33:00 +0200 [thread overview]
Message-ID: <85tzpval6b.fsf@lola.goethe.zz> (raw)
In-Reply-To: <6bcc356f0709151014j9606a3ape6b62770304560ba@mail.gmail.com> (Nikodemus Siivola's message of "Sat\, 15 Sep 2007 20\:14\:51 +0300")
"Nikodemus Siivola" <nikodemus@random-state.net> writes:
> On 9/15/07, David Kastrup <dak@gnu.org> wrote:
>
>> "Take a while"? What's wrong with git-reflog?
>
> Not needing it as a part of my regular workflow, and therefore
> not thinking about it. *blush*
"Oh no, what have I done now?"
I am afraid that working with git still exposes me to this question
time and again. And git-reflog usually provides the answer, as well
as what I need to recover.
--
David Kastrup, Kriemhildstr. 15, 44793 Bochum
prev parent reply other threads:[~2007-09-15 17:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2a8a071a0709140028o472bcr8c82bd88e37cc4e9@mail.gmail.com>
[not found] ` <2a8a071a0709140036l5db62c0fl5af01f75f35610ba@mail.gmail.com>
[not found] ` <7vk5qtd3le.fsf@gitster.siamese.dyndns.org>
2007-09-15 0:40 ` Data Integrity & un-Commited Branches Brian Scott Dobrovodsky
2007-09-15 2:51 ` Shawn O. Pearce
2007-09-15 6:24 ` Brian Scott Dobrovodsky
2007-09-15 6:32 ` Shawn O. Pearce
2007-09-15 6:37 ` Junio C Hamano
2007-09-15 7:14 ` Brian Scott Dobrovodsky
2007-09-15 7:38 ` Jan Hudec
2007-09-15 7:51 ` Shawn O. Pearce
2007-09-15 13:11 ` Nikodemus Siivola
2007-09-15 13:59 ` David Kastrup
2007-09-15 17:14 ` Nikodemus Siivola
2007-09-15 17:33 ` David Kastrup [this message]
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=85tzpval6b.fsf@lola.goethe.zz \
--to=dak@gnu.org \
--cc=brian@pontech.com \
--cc=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=nikodemus@random-state.net \
--cc=spearce@spearce.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 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.