- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Feb 19 2016
added a newline @brueffer
Feb 18 2016
address comments
Since the working is being discussed, I chose a different path as I felt the statement was rather wordy. I attempted to tighten it.
address comments
This can be addressed with other content update, in my opinion. I would like to change the wording of the new content, but then go back and address other content.
It also seems odd to me that we are mentioning the "package from ports"... ports are not packages, and packages are not ports, but you need ports to make packages :)
Feb 16 2016
I thought I would be addressing this, but looks like others are now looking into it, as well? I'm not sure what the status of this is now....
Feb 12 2016
Feb 11 2016
I believe what this is trying to address, though, is respecting a library choice between BASE vs. PORT/PKG throughout the build process. The way it is now, I don't believe that is accomplished.
Feb 4 2016
Feb 3 2016
Jan 30 2016
Jan 29 2016
In D5118#108942, @wblock wrote:
address comments
The procedure was tested as part of the documentation change.
Jan 28 2016
addressed comments from Warren for Hungarian and Netherlands builds
Jan 27 2016
Any comments, thoughts, suggestions on this review?
Thanks. -jgh
Jan 26 2016
I understand, however it is unfortunate as I am finding all of the security bulletins, so far, in place in the new location.
Jan 25 2016
Upon doing more research, I found the company is now Teklinks.
Updated diff.
Jan 23 2016
Looks good to me. If it passes qa and build, go ahead with the commit.
Jan 20 2016
Jan 16 2016
Jan 15 2016
Dec 21 2015
Oct 14 2015
Oct 5 2015
It is noted in the bug title, itself.
"Fixed documentation grammar"
updating style per request
addressed concern
Oct 2 2015
Oct 1 2015
this article is gone as of r46450
i wasn't see my new diff. so uploaded, again.