From: Rod Whitby <rod@whitby.id.au>
To: openembedded-devel@lists.openembedded.org
Subject: Re: git master not updating
Date: Thu, 02 Oct 2008 09:00:53 +0930 [thread overview]
Message-ID: <48E4082D.9030000@whitby.id.au> (raw)
In-Reply-To: <gc017m$gq4$1@ger.gmane.org>
Koen Kooi wrote:
> On 01-10-2008 15:34, Nicola Mfb wrote:
>> 2008/10/1 Kalev Lember<kalev@smartlink.ee>
>> [...]
>>
>>> 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.
>>
>> Yes, the same here, i opened one of those bugs.
>> I'm using a semiautomated makefile environment for fso/openmoko, this use
>> git and not monotone, so this problem affects a lot of peoples, please fix!
>
> That's what you get for using makefiles....
A typical response from Koen. Sigh. For once it would be good for him
to focus on the problem at hand (which was reported correctly with no
mention of makefiles) instead of trying to take childish potshots at
things he has a personal vendetta against.
A number of places on the internet (including
http://elinux.org/BeagleBoardAndOpenEmbeddedGit,
http://wiki.openembedded.net/index.php/Git,
http://wiki.neurostechnology.com/index.php/OpenEmbedded_OSD2,
http://linux.paduli.org/index.php?title=OpenEmbedded%2C_linux%2C_software_e_sviluppo_per_dispositivi_embedded!,
just for some examples) advise users to type the following command to
clone the trial OE git repo, with no mention of needing a specific branch:
git clone git://git.openembedded.net/org.openembedded.dev/
In fact, Koen himself advised users to use exactly that command (and no
mention of needing to check out a specific branch) in the #beagle IRC
channel on 14th June 2008 (see
http://www.beagleboard.org/irclogs/index.php?date=2008-06-14 at [12:43:48]).
That used to work, and now it doesn't, due to an unannounced change to
the operation of the trial OE git repo.
Note that I've been careful to say "trial OE git repo" everywhere, since
it's still a trial and there is no official OE documentation on whether
you should be pulling from the master branch or the org.openembedded.dev
branch (and as can be seen from the BeagleBoard page above, and Koen's
instructions to people on the #beagle IRC channel, the confusion exists
independently of whether a makefile is used or not). So anyone using
the trial OE git repo does so at their own risk.
The beauty of a makefile is that *everyone* using it can be migrated to
the latest correct instructions for using the trial OE git repo
automatically.
Koen, are you going to go around and fix all the places on the internet
that have propagated the obsolete instructions on how to use the trial
OE git repo (including the IRC log where you yourself gave those
obsolete instructions)?
I'll be doing so today for all users of the Makefiles who are affected
by this change in how the trial OE git repo should be accessed.
-- Rod
next prev parent reply other threads:[~2008-10-01 23:35 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
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 [this message]
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=48E4082D.9030000@whitby.id.au \
--to=rod@whitby.id.au \
--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.