All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalev Lember <kalev@smartlink.ee>
To: openembedded-devel@lists.openembedded.org
Subject: Re: git master not updating
Date: Wed, 01 Oct 2008 16:07:58 +0300	[thread overview]
Message-ID: <48E3762E.6000203@smartlink.ee> (raw)
In-Reply-To: <873ajglc0d.fsf@neumann.lab.ossystems.com.br>

Otavio Salvador wrote:
> Kalev Lember <kalev@smartlink.ee> writes:
>
>   
>> Hello,
>>
>> http://gitweb.openembedded.net/?p=org.openembedded.dev.git;a=summary
>> The master head of org.openembedded.dev is not updating. I already
>> spotted two bug reports (4584 and 4590) which reported issues that were
>> fixed in monotone 4 days ago, but never got into git master.
>>     
>
> org.openembedded.dev branch is up to date. I'm using it.
>
>   
Well yes, but if you just do:
git clone git://git.openembedded.net/org.openembedded.dev

you'll end up on master branch, which is not updating.

$ git clone git://git.openembedded.net/org.openembedded.dev
Initialized empty Git repository in
/home/kalev/tmp/org.openembedded.dev/.git/
remote: Counting objects: 172765, done.
remote: Compressing objects: 100% (66031/66031), done.
remote: Total 172765 (delta 117875), reused 155868 (delta 106016)
Receiving objects: 100% (172765/172765), 81.65 MiB | 1116 KiB/s, done.
Resolving deltas: 100% (117875/117875), done.
Checking out files: 100% (20330/20330), done.
$ cd org.openembedded.dev/
$ git status
# On branch master
nothing to commit (working directory clean)
$ git log | head
commit af6706689123f82a525f2f716cbc54b3e9154814
Author:  <koen@openembedded.org>
Date:   Fri Sep 26 16:03:59 2008 +0000

    feed browser: add screenshot support, update angstrom sample config

commit 44b0c01116c767d57a648981f8d57133fefc7954
Author:  <koen@openembedded.org>
Date:   Fri Sep 26 15:04:45 2008 +0000


-- 
Kalev



  reply	other threads:[~2008-10-01 13:12 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-01 12:24 git master not updating Kalev Lember
2008-10-01 12:45 ` Otavio Salvador
2008-10-01 13:07   ` Kalev Lember [this message]
2008-10-01 13:18     ` Otavio Salvador
2008-10-01 13:34     ` Nicola Mfb
2008-10-01 14:24       ` Koen Kooi
2008-10-01 15:48         ` Mike (mwester)
2008-10-01 16:39           ` Andrea Adami
2008-10-01 17:13           ` Philip Balister
2008-10-01 18:32             ` Nicola Mfb
2008-10-01 23:33             ` Rod Whitby
2008-10-01 17:17           ` Koen Kooi
2008-10-01 18:11             ` Mike (mwester)
2008-10-01 18:43             ` Tom Rini
2008-10-01 20:18               ` Koen Kooi
2008-10-01 21:36                 ` Tom Rini
2008-10-01 23:57                   ` Rod Whitby
2008-10-01 23:30         ` Rod Whitby
2008-10-02  0:43           ` I'm sick of that Was " Holger Freyther
2008-10-02  1:50             ` Otavio Salvador
2008-10-02  1:51             ` Rod Whitby
2008-10-02 11:49             ` Cliff Brake
2008-10-02 12:51               ` Kalev Lember
2008-10-02 18:06             ` Mark Vels
2008-10-02 20:29               ` Rodrigo Vivi
2008-10-02 22:15             ` Michael Krelin
2008-10-02  0:36 ` Holger Freyther
2008-10-02 11:28   ` Cliff Brake
2008-10-03  2:55     ` Holger Freyther

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=48E3762E.6000203@smartlink.ee \
    --to=kalev@smartlink.ee \
    --cc=openembedded-devel@lists.openembedded.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 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.