From: Andrew Walrond <andrew@walrond.org>
To: Thomas Rast <trast@inf.ethz.ch>
Cc: git@vger.kernel.org
Subject: Re: Bug report: stash in upstream caused remote fetch to fail
Date: Wed, 1 Feb 2012 22:37:44 +0000 [thread overview]
Message-ID: <20120201223743.GC2431@localhost.localdomain> (raw)
In-Reply-To: <874nvap9hj.fsf@thomas.inf.ethz.ch>
On Wed, Feb 01, 2012 at 09:46:48PM +0100, Thomas Rast wrote:
>
> Do you, by any chance, still have a copy of the upstream repo before you
> trashed the stash? It would be interesting to know whether there was
> actually some repository corruption going on (that went unnoticed by
> fsck, no less) or if there was a bug in the transmission.
I tried to reproduce the problem but without success :(
Disk corruption is unlikely - raided drives etc etc. More likely stash
related somehow as I was applying patches manually on older versions
checked out in a temp branch, stashing the results then applying the
stash onto master/HEAD.
But why was a remote clone involved with the upstream stash at all I
wonder??
Andrew Walrond
next prev parent reply other threads:[~2012-02-01 22:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-01 16:59 Bug report: stash in upstream caused remote fetch to fail Andrew Walrond
[not found] ` <874nvap9hj.fsf@thomas.inf.ethz.ch>
2012-02-01 22:37 ` Andrew Walrond [this message]
-- strict thread matches above, loose matches on Subject: below --
2014-01-03 21:12 Matt Burke
2014-01-06 15:27 ` Jeff King
2014-01-06 16:16 ` Junio C Hamano
2014-01-06 19:36 ` Jeff King
2014-01-06 20:17 ` Junio C Hamano
2014-01-06 23:03 ` Jeff King
2014-01-06 23:22 ` Junio C Hamano
2014-01-07 3:19 ` Junio C Hamano
2014-01-15 10:46 ` Jeff King
2014-01-15 10:48 ` Jeff King
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=20120201223743.GC2431@localhost.localdomain \
--to=andrew@walrond.org \
--cc=git@vger.kernel.org \
--cc=trast@inf.ethz.ch \
/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.