All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Mike (mwester)" <mwester@dls.net>
To: openembedded-devel@openembedded.org
Subject: Re: git master not updating
Date: Wed, 01 Oct 2008 13:11:04 -0500	[thread overview]
Message-ID: <48E3BD38.2080708@dls.net> (raw)
In-Reply-To: <gc0bc5$o9o$2@ger.gmane.org>

Koen Kooi wrote:
> On 01-10-2008 17:48, Mike (mwester) wrote:
>> 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....
>>
>> How does a makefile affect the branches not being updated?
> 
> All org.openembedded.* branches are still being updated.
>

Yes?  And how does a wrapper of any sort, makefile or shell script,
affect that?  Are you saying the bitbake and OE have code to detect if
"make" is a parent process, and it behaves differently?  Or are you
saying that "make" is broken?  Or are their unknown bugs in bitbake or
OE recipes that seem to behave badly when bitbake is invoked by "make"?

Of course it's none of the above  -- it's that you despise the makefile
--  but a lot of other people might actually think you are making some
technically-sound point, and wrongly determine that OE and make are
incompatible in some way.

So why not just say that the wrong branch is being pulled instead of
making snide comments about the tools others use?

Mike (mwester)



  reply	other threads:[~2008-10-01 18:16 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) [this message]
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=48E3BD38.2080708@dls.net \
    --to=mwester@dls.net \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@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.