From: Bob Cochran <yocto@mindchasers.com>
To: "Rifenbark, Scott M" <scott.m.rifenbark@intel.com>
Cc: Yocto discussion list <yocto@yoctoproject.org>
Subject: Re: dev manual has broken "git workflows" link, what should replace it?
Date: Wed, 07 Mar 2012 11:17:38 -0500 [thread overview]
Message-ID: <4F578A22.6060602@mindchasers.com> (raw)
In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB123793B744443@ORSMSX101.amr.corp.intel.com>
Robert has done a great job pointing out issues and problems with the
documentation. Shouldn't the issues that are clearly breaks (like a
broken link) be entered into bugzilla?
https://bugzilla.yoctoproject.org/describecomponents.cgi?product=Documentation
On 03/07/2012 11:10 AM, Rifenbark, Scott M wrote:
> I sent an email requesting a merge/pull from yocto-docs into poky/documentation yesterday. I looked at the last documentation commit in poky/documentation and it was dated January 6. They are quite a bit out of sync.
>
> Scott
>
> -----Original Message-----
> From: Robert P. J. Day [mailto:rpjday@crashcourse.ca]
> Sent: Wednesday, March 07, 2012 9:41 AM
> To: Rifenbark, Scott M
> Cc: Yocto discussion list
> Subject: RE: [yocto] dev manual has broken "git workflows" link, what should replace it?
>
> On Wed, 7 Mar 2012, Rifenbark, Scott M wrote:
>
>> This area in the document has been re-worked and the bad link does
>> not exist in the
>> http://www.yoctoproject.org/docs/latest/dev-manual/dev-manual.html
>> version (master) of the document.
>
> i'm sure you've answered this before, but how far behind is the docs
> repo from the general yocto dev repo? i simply use the yocto
> development checkout for my work, so that's what i'm picking up for
> docs. and give that it's development, it would seem that commits
> shouldn't languish very long in the docs repo before being pushed.
>
> what's the general time lag?
>
> rday
>
next prev parent reply other threads:[~2012-03-07 16:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-07 10:59 dev manual has broken "git workflows" link, what should replace it? Robert P. J. Day
2012-03-07 13:58 ` Rifenbark, Scott M
2012-03-07 15:41 ` Robert P. J. Day
2012-03-07 16:10 ` Rifenbark, Scott M
2012-03-07 16:17 ` Bob Cochran [this message]
2012-03-07 16:42 ` Robert P. J. Day
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=4F578A22.6060602@mindchasers.com \
--to=yocto@mindchasers.com \
--cc=scott.m.rifenbark@intel.com \
--cc=yocto@yoctoproject.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.