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:03:48 +0930 [thread overview]
Message-ID: <48E408DC.80509@whitby.id.au> (raw)
In-Reply-To: <48E3AFB5.5000600@balister.org>
Philip Balister wrote:
> The problem is that if someone has a problem and shows up in #oe asking
> why there are not any updates. If they can't explain the actual command
> to do the updates, most of the people in #oe cannot help.
The actual git commands executed are printed in the shell where the
makefile is run. And you can be sure that they haven't just made a typo
in the git commands, cause it's part of a makefile.
As always, the first thing a user should include in a bug report is a
trace of the execution of the command that is failing. That will
clearly show the git commands executed.
-- Rod
next prev parent reply other threads:[~2008-10-01 23:38 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 [this message]
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=48E408DC.80509@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox