From: Linus Torvalds <torvalds@linux-foundation.org>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [git pull] vfs pile 2
Date: Thu, 17 Dec 2009 08:39:14 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.2.00.0912170831030.15740@localhost.localdomain> (raw)
In-Reply-To: <20091217162454.GA18217@ZenIV.linux.org.uk>
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?
It has a few very annoying things, the first and foremost of which is that
HEAD points to some crazy branch (new-truncate).
So when you do "git pull" without mentioning the branch (which is the
normal behavior) and would expect to get your default thing (which was
also what you asked me to pull in your original pull request), you instead
get some totally inexplicable old random crud.
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.
(It also has FETCH_HEAD, index, COMMIT_EDITMSG etc - all things that don't
make sense in a bare repository)
Linus
next prev parent reply other threads:[~2009-12-17 16:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 16:24 Al Viro
2009-12-17 16:39 ` Linus Torvalds [this message]
2009-12-17 18:03 ` Al Viro
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=alpine.LFD.2.00.0912170831030.15740@localhost.localdomain \
--to=torvalds@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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
all inboxes | Powered by JetHome®