From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [git pull] vfs pile 2
Date: Thu, 17 Dec 2009 18:03:19 +0000 [thread overview]
Message-ID: <20091217180319.GB18217@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.0912170831030.15740@localhost.localdomain>
On Thu, Dec 17, 2009 at 08:39:14AM -0800, Linus Torvalds wrote:
>
>
> On Thu, 17 Dec 2009, Al Viro wrote:
> >
> > Misc bits and pieces, cleaning the table for scaling stuff...
> > Please, pull from
> > git.kernel.org/pub/scm/linux/kernel/git/viro/vfs-2.6.git/ master
> > in a few minutes (or directly from hera)
>
> Btw, would you mind cleaning that repo up?
Sure.
> That's really unexpected for a bare repository. I spent some time looking
> at the odd conflicts the other day when I pulled originally.
>
> I suspect you just did a "scp -rp" or something to initially set it up,
> which is why it contains some random branch - that just happened to be
> your active branch at the time you did that setup.
IIRC, it was _way_ back and done as git clone -l -s <your tree> vfs-2.6
followed by mv vfs-2.6/.git /pub/scm/...../vfs-2.6.git. So it probably
_isn't_ a proper bare repository in the first place.
OK... I've edited config a bit, set HEAD to ref: refs/heads/master and
tried to clean the things up. What I still don't understand is why the
hell does it have an apparently unkillable dangling commit that seems
to be yours, despite having alternates pointing to your tree. *And*
a bunch of loose objects sitting around and impossible to get rid of...
next prev parent reply other threads:[~2009-12-17 18:03 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 16:24 [git pull] vfs pile 2 Al Viro
2009-12-17 16:39 ` Linus Torvalds
2009-12-17 18:03 ` Al Viro [this message]
2009-12-17 18:16 ` Linus Torvalds
2009-12-17 18:39 ` Al Viro
2009-12-17 21:22 ` Linus Torvalds
2009-12-17 21:43 ` Al Viro
2009-12-17 21:58 ` Linus Torvalds
2010-10-29 13:25 [git pull] vfs, " Al Viro
2016-08-06 1:36 [git pull] vfs " Al Viro
2018-06-04 1:02 [git pull] vfs, " Al Viro
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=20091217180319.GB18217@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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).