From: Mauro Carvalho Chehab <mchehab@infradead.org>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: linux-next@vger.kernel.org, "Igor M. Liplianin" <liplianin@netup.ru>
Subject: Re: linux-next: v4l-dvb tree build failure
Date: Thu, 5 Mar 2009 22:15:14 -0300 [thread overview]
Message-ID: <20090305221514.66f308ff@pedra.chehab.org> (raw)
In-Reply-To: <20090306110548.9ef01100.sfr@canb.auug.org.au>
On Fri, 6 Mar 2009 11:05:48 +1100
Stephen Rothwell <sfr@canb.auug.org.au> wrote:
> Hi Mauro,
>
> On Thu, 5 Mar 2009 18:51:50 -0300 Mauro Carvalho Chehab <mchehab@infradead.org> wrote:
> >
> > Fixed.
>
> Thanks.
>
> > From time to time, I got an weird message like this when updating my remote
> > repository:
> >
> > $ git --git-dir /home/v4l/tokernel/bare/linux-next.git push -f origin
> > Counting objects: 194, done.
> > Compressing objects: 100% (70/70), done.
> > Writing objects: 100% (93/93), 14.19 KiB, done.
> > Total 93 (delta 82), reused 24 (delta 23)
> > warning: updating the currently checked out branch; this may cause confusion,
> > as the index and working tree do not reflect changes that are now in HEAD.
> > To ssh://master.kernel.org/pub/scm/linux/kernel/git/mchehab/linux-next.git
> >
> > What's more weird is that I never touch directly
> > on /home/v4l/tokernel/bare/linux-next.git, since this is just a local bare
> > tree. My procedure is to update the patches on a work tree, then push it to the
> > bare repository and then to kernel.org.
>
> Is there some reason that you repo on kernel.org is not bare as well?
It is bare...
Hmm... at config, it were marked with bare = false, not sure why.
Anyway, I manually Fixed config. It seemed to solve the issue.
Thanks!
Cheers,
Mauro
next prev parent reply other threads:[~2009-03-06 1:15 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-05 0:35 linux-next: v4l-dvb tree build failure Stephen Rothwell
2009-03-05 21:51 ` Mauro Carvalho Chehab
2009-03-06 0:05 ` Stephen Rothwell
2009-03-06 1:15 ` Mauro Carvalho Chehab [this message]
-- strict thread matches above, loose matches on Subject: below --
2010-01-27 6:59 Stephen Rothwell
2010-01-27 23:24 ` Andy Walls
2010-01-28 1:54 ` Mauro Carvalho Chehab
2010-01-28 5:24 ` Stephen Rothwell
2009-04-07 0:58 Stephen Rothwell
2009-04-07 1:20 ` Mauro Carvalho Chehab
2009-04-07 4:47 ` Stephen Rothwell
2009-03-27 0:40 Stephen Rothwell
2009-03-27 11:28 ` Mauro Carvalho Chehab
2009-03-27 14:03 ` Stephen Rothwell
2009-03-02 0:05 Stephen Rothwell
2009-03-02 0:08 ` Michael Krufky
2009-03-02 0:30 ` Stephen Rothwell
2009-03-02 2:52 ` Mauro Carvalho Chehab
2008-12-08 2:07 Stephen Rothwell
2008-12-01 23:37 Stephen Rothwell
2008-12-02 10:03 ` Mauro Carvalho Chehab
2008-12-02 22:23 ` Stephen Rothwell
2008-12-03 22:48 ` Mauro Carvalho Chehab
2008-12-03 0:08 ` Stephen Rothwell
2008-12-03 22:49 ` Mauro Carvalho Chehab
2008-11-25 4:41 Stephen Rothwell
2008-11-07 3:30 Stephen Rothwell
2008-11-07 17:43 ` Harvey Harrison
2008-11-07 18:41 ` Greg KH
2008-11-07 23:02 ` Stephen Rothwell
2008-11-12 0:54 ` Mauro Carvalho Chehab
2008-11-12 22:45 ` Greg KH
2008-11-07 22:59 ` Stephen Rothwell
2008-11-07 23:06 ` Greg KH
2008-11-08 3:05 ` Sam Ravnborg
2008-11-08 4:38 ` Greg KH
2008-11-08 5:08 ` Greg KH
2008-10-29 2:20 Stephen Rothwell
2008-10-29 12:26 ` Andreas Oberritter
2008-11-03 1:52 ` Stephen Rothwell
2008-11-05 1:57 ` Stephen Rothwell
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=20090305221514.66f308ff@pedra.chehab.org \
--to=mchehab@infradead.org \
--cc=linux-next@vger.kernel.org \
--cc=liplianin@netup.ru \
--cc=sfr@canb.auug.org.au \
/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).