linux-kernel - Re: [git pull] vfs pile 2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 17 Dec 2009 18:03:19 +0000
From:	Al Viro <viro@...IV.linux.org.uk>
To:	Linus Torvalds <torvalds@...ux-foundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [git pull] vfs pile 2

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...
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/