From: Chris Hatton <christopherhattonuk@gmail.com>
To: git@vger.kernel.org
Subject: Another casualty
Date: Tue, 10 Jan 2012 14:08:38 +0000 (UTC) [thread overview]
Message-ID: <loom.20120110T150742-201@post.gmane.org> (raw)
In-Reply-To: m3zkhe16bu.fsf@localhost.localdomain
3 hours-worth of work just got whacked by this bug. Unimpressed :-(
Could have been worse I suppose. Thanks for the confirmation.
<Goes to update Git>
prev parent reply other threads:[~2012-01-10 14:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 14:08 Merge seems to overwrite unstaged local changes Sebastian Schuberth
2011-09-28 15:25 ` Junio C Hamano
2011-09-29 13:07 ` Sebastian Schuberth
2011-10-06 13:27 ` Sebastian Schuberth
2011-10-06 15:35 ` Jakub Narebski
2012-01-10 14:08 ` Chris Hatton [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=loom.20120110T150742-201@post.gmane.org \
--to=christopherhattonuk@gmail.com \
--cc=git@vger.kernel.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.