All of lore.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: Petr Baudis <pasky@suse.cz>
Cc: "Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>,
	Ming Ming Cao <cmm@us.ibm.com>,
	"linux-ext4@vger.kernel.org" <linux-ext4@vger.kernel.org>,
	git@vger.kernel.org
Subject: Re: Ext4 patchqueue corrupted ?
Date: Fri, 11 Jul 2008 08:26:17 -0400	[thread overview]
Message-ID: <20080711122617.GA8154@mit.edu> (raw)
In-Reply-To: <20080711084715.GT10151@machine.or.cz>

On Fri, Jul 11, 2008 at 10:47:15AM +0200, Petr Baudis wrote:
>   very puzzling; I have backed up the broken objects store, can you
> repush, please? I'm curious about how this could have happenned;
> repo.or.cz now uses Git from latest next, which is a rather strange
> coincidence. ;-) Or did any of the pushers do anything special about
> pushin to the repository recently?

Aneesh, did you try repushing?  It looks like the objects store is
broken again.

Pasky, in case it helps, and for the benefit of Linux-ext4 folks, I
have a copy of my repository (which I last pushed to repo.or.cz around
noon US/Eastern yesterday) here:

     git://git.kernel.org/pub/scm/fs/ext2/ext4-patch-queue.git

My most recent HEAD is ec90e411; if anyone has something more recent,
they can send it to me via:

     git bundle create /tmp/to-send ec90e411

... and then e-mailing me as an attachment the resulting binary file
in /tmp/to-send.

						- Ted

  reply	other threads:[~2008-07-11 12:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-11  3:46 Ext4 patchqueue corrupted ? Aneesh Kumar K.V
2008-07-11  8:47 ` Petr Baudis
2008-07-11 12:26   ` Theodore Tso [this message]
2008-07-11 12:31     ` Aneesh Kumar K.V
2008-07-11 12:47       ` Theodore Tso
2008-07-11 13:13         ` Petr Baudis

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=20080711122617.GA8154@mit.edu \
    --to=tytso@mit.edu \
    --cc=aneesh.kumar@linux.vnet.ibm.com \
    --cc=cmm@us.ibm.com \
    --cc=git@vger.kernel.org \
    --cc=linux-ext4@vger.kernel.org \
    --cc=pasky@suse.cz \
    /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.