text:
Difference between revisions of "Submitting Xen Project Patches"
Lars.kurth (talk | contribs)
(→Common modifications to the Subject Prefix: Add for-next)
Lars.kurth (talk | contribs)
(→Step 3: Send patches using git send-email: Fixed typo -to > --to)
|Line 415:
|Line 415:
Send the patches using
Send the patches using
<syntaxhighlight lang="sh" highlight="1">
<syntaxhighlight lang="sh" highlight="1">
$ git send-email -to email@example.com ../patches/feature-v2/*.patch
$ git send-email -to firstname.lastname@example.com ../patches/feature-v2/*.patch
Revision as of 19:37, 26 September 2019
This document assumes that you have cloned xen.git (or a similar repository) and that you have some development patches ready to submit. If you are not familiar with git and Xen Development branches, read the following documents
- Xen Project Repositories
- Managing Xen Patches with Git
- Managing Xen Patches with StGit
- Managing Xen Patches with_Git-series
This document outlines the code submission process primarily to the xen-devel@ mailing list. The process does also apply to other mailing list based subprojects: specific information related to these subprojects can be found at the bottom of this document.
- 1 What is in a patch and a patch series?
- 1.1 What is in a patch?
- 1.1.1 Title and description of the patch
- 1.1.2 Signed-off-by
- 1.1.3 Other *-by tags
- 1.1.4 CC lists of the maintainers or reviewers for the patch
- 1.1.5 Change log (for patch revisions >= 2)
- 1.1.6 Information that is useful for the reviewer, which you do not want in the final commit messages
- 1.1.7 A version number and subject prefix
- 1.1.8 Example patch
- 1.2 What is in a patch series?
- 1.1 What is in a patch?
- 2 Sending the patches to the list
- 2.1 Setting up git send-email
- 2.2 Settings that help save you time
- 2.3 Subject Prefix
- 2.4 Sending a Patch Series
- 2.5 Sending an individual patch
- 2.6 Using add_maintainers.pl (or get_maintainer.pl) from outside of xen.git
- 3 Review, Rinse & Repeat
- 4 Workflow for related repositories and projects
What is in a patch and a patch series?
Changes to the Xen Project are submitted to a mailing list either as an individual patch or as a patch series. A patch series is a series of patches that are related and broken into a logical series of individual patches.
Patches, if accepted, will turn into commits in the git source tree. However, frequently multiple versions of patches will have to be posted, before the patch is accepted.
There are three groups of people to think about when writing the patch and the commit message:
- Reviewers on the mailing list, who are trying to understand what your patch does, if it's correct, and what side effects it will have.
- People skimming through changesets deciding if a patch is important for them to look at for backporting, review, implications on out-of-tree patches, &c.
- Someone in the perhaps distant future, who is trying to understand why the code is the way it is.
Try to make your patches with all of these people in mind.
What is in a patch?
A patch is an e-mail, which is generated from a single commit in your git tree and augmented by using a tool (e.g. git-format, add_maintainers.pl, git-send-email) which may prompt you to edit the final e-mail manually.
It is important to note, that your patch will inherit the following information from the git commit message on which it is based, assuming you recorded the information in the commit message at commit time
- Title and description
- Signed-off-by
- Other *-by tags such as Reported-by
- CC lists of reviewers - these can be added automatically later
- Change log and other information that is useful for the reviewer
Title and description of the patch
- The first line the top of the patch should contain a short description of what the patch does, and hints as to what code it touches. It typically contains a prefix, such as xen/x86:, xen/arm:, tools:, etc. Note that maintainers may propose a different prefix or change it at commit-time if it isn't correct
- The description should be useful for both the reviewers and people in the future trying to understand what the patch does. It can be as short as
Code cleanup -- no functional changes, or as long as it takes to accurately describe the bug you are trying to solve or the new functionality you are introducing.
The description should be wrapped to a maximum of 80 columns, unless it includes an error message which is longer than 80 characters.
All patches to the Xen Project code base must include the line Signed-off-by: your_name <your_email> at the end of the change description.
You can use -s or --signoff when committing a patch, if you change your default settings as outlined here.
This is required and indicates that you certify the patch under the "Developer's Certificate of Origin" which states:
Developer's Certificate of Origin 1.1
By making a contribution to this project, I certify that:
(a) The contribution was created in whole or in part by me and I
have the right to submit it under the open source license
indicated in the file; or
(b) The contribution is based upon previous work that, to the best
of my knowledge, is covered under an appropriate open source
license and I have the right under that license to submit that
work with modifications, whether created in whole or in part
by me, under the same open source license (unless I am
permitted to submit under a different license), as indicated
in the file; or
(c) The contribution was provided directly to me by some other
person who certified (a), (b) or (c) and I have not modified
(d) I understand and agree that this project and the contribution
are public and that a record of the contribution (including all
personal information I submit with it, including my sign-off) is
maintained indefinitely and may be redistributed consistent with
this project or the open source license(s) involved.
You may add the following git tags before or after the signed-off-by tag:
- Reported-by: is used to credit someone who found the bug that the patch attempts to fix
- Tested-by: is used to indicate that the listed person applied the patch and found it to have the desired effect.
Later in the review process, your patch or patch series may accumulate tags, such as
- Acked-by: a maintainer of the patch reviewed the patch and found it is good to go in.
- Reviewed-by: another community member, a designated reviewer or a maintainer of another component reviewed the patch
Note that if there are several revisions of a patch, you ought to copy tags that have accumulated during the review. For example, if person A and person B added a Reviewed-by: tags to v1 of your patch, include it into v2 of your patch. If you make substantial changes after certain tags were already applied, you will want to consider which ones are no longer applicable (and may require re-providing).
CC lists of the maintainers or reviewers for the patch
- Always send a copy of the patch to (via CC) the maintainer of the code you are modifying. The maintainers and reviewers are listed in the MAINTAINERS file at the top of the Xen tree. If no maintainer is listed then the maintainers listed under THE REST in the MAINTAINERS file
- Note that if you follow the steps described in this document, the add_maintainers.pl/get_maintainer.pl scripts will add the correct people automatically
- If any people who were not on the CC list for an earlier review, but have reviewed your patch, you may want to manually add them (via CC) to the CC list.
Change log (for patch revisions >= 2)
Changes to previous versions of a patch are recorded in the patch commit message after the CC lists. These are required to be very detailed and will help the reviewer to check whether changes have been addressed. An example of a change log can be found below (the actual patch for this example is here).
Changes in v4:
- ARM -> Arm
- libxl__memory_policy_to_xc -> libxl__arch_memory_policy_to_xc
- keep Arm policies together
Changes in v3:
- s/nGRE/nGnRE/g
- s/LIBXL_MEMORY_POLICY_ARM_DEV_NGRE/LIBXL_MEMORY_POLICY_ARM_DEV_NGNRE/g
- s/arm_devmem/arm_dev_nGnRE/g
- s/arm_memory/arm_mem_WB/g
- improve commit message
- improve man page
- s/MEMORY_POLICY_X86_UC/MEMORY_POLICY_X86_UC_MINUS/g
- s/x86_uc/x86_UC_minus/g
- move security support clarification to a separate patch
Changes in v2:
- add #define LIBXL_HAVE_MEMORY_POLICY
- ability to part the memory policy parameter even if gfn is not passed
- rename cache_policy to memory policy
- rename MEMORY_POLICY_DEVMEM to MEMORY_POLICY_ARM_DEV_nGRE
- rename MEMORY_POLICY_MEMORY to MEMORY_POLICY_ARM_MEM_WB
- rename memory to arm_memory and devmem to arm_devmem
- expand the non-security support status to non device passthrough iomem
- rename iomem options
- add x86 specific iomem option
Information that is useful for the reviewer, which you do not want in the final commit messages
You can manually add additional information that you do not want to appear in the commit message, after the maintainers list. An example can be found in this patch.
A version number and subject prefix
Each patch contains a revision number, or a subject prefix. For example, a patch email may contain [RFC PATCH v2] or [PATCH v3 4/11] indicating that the patch is part of a patch series.
Example patch
The example patch here that resulted in the following commit.
1 vif-common.sh: Have iptables wait for the xtables lock permalink
3 iptables has a system-wide lock on the xtables. Strangely though, in
4 the case of two concurrent invocations, the default is for the
5 instance not grabbing the lock to exit out rather than waiting for it.
6 This means that when starting a large number of guests in parallel,
7 many will fail out with messages like this:
9 2017-05-10 11:45:40 UTC libxl: error: libxl_exec.c:118: libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge remove [18767] exited with error status 4
10 2017-05-10 11:50:52 UTC libxl: error: libxl_exec.c:118: libxl_report_child_exitstatus: /etc/xen/scripts/vif-bridge offline [1554] exited with error status 4
12 In order to instruct iptables to wait for the lock, you have to
13 specify '-w'. Unfortunately, not all versions of iptables have the
14 '-w' option, so on first invocation check to see if it accepts the -w
15 command.
17 Reported-by: Antony Saba <aws...@gmail.com>
18 Signed-off-by: George Dunlap <geor...@citrix.com>
19 ---
20 Cc: Ian Jackson <ian....@citrix.com>
21 Cc: Wei Liu <wei....@citrix.com>
22 ---
23 tools/hotplug/Linux/vif-common.sh | 38 +++++++++++++++++++++++++++++++++++---
24 1 file changed, 35 insertions(+), 3 deletions(-)
26 diff --git a/tools/hotplug/Linux/vif-common.sh
27 b/tools/hotplug/Linux/vif-common.sh
28 index 6e8d584..29cd8dd 100644
29 --- a/tools/hotplug/Linux/vif-common.sh
30 ...
- Lines 1 to 15: A good patch description answers the following questions
- What is the situation
- Why is the current situation a problem
- How does this patch fix the problem
- Anything else the reviewers need to know to understand the patch
- Lines 17 to 18: Contains the *by tags including the mandatory Signed-off-by tag
- Lines 20 to 21: Contains CC statements of the maintainers. Note that these can be added manually, but if you follow the steps below these will be added automatically
- Before Line 22: added in lines before the
- After Line 22: This is the actual code patch
What is in a patch series?
A patch series is a sequence of threaded emails, which are generated from multiple git commits (typically the last N ones) in your git tree and augmented by using a tool (e.g.
git-send-email) which may prompt you to edit the final email manually.
Patch series can be anything from bug fixes or small improvements that are too big for an individual patch or encompass different components (e.g. hypervisor, toolstack change and a docs change) to new features with 10s of patches spanning multiple components.
In addition to the individual patches, which describe the patches making up the series, a patch series must contain a cover letter as the first email in the series. If you want any of the automated tooling which we use on xen-devel@ to work, the patch series must be threaded, with the cover letter the parent and each individual patch being a child of the cover letter.
Break down your patches appropriately
- Each patch in a patch series should preferably do one logical thing (or one related set of things). The goal is for reviewers to understand the change that each patch is making with a minimum of effort.
- No patch should ever break existing functionality.
- Never fix bugs in one of your patches by changing it in a later patch; go back and change the patch with the bug in it.
- Don't mix clean-up patches (which make things look prettier or refactor but don't change functionality) with code-change patches. However, e.g. style corrections on lines changed anyway are generally accepted (and often welcomed). Clean-up patches should be clearly marked as having no functional changes.
Cover letter
Cover letters are an important part of a patch series. The Xen Project has high standards when it comes to large and complex series. The cover letter should cover the following information
- It should contain an explanation of what you are trying to achieve
- It should explain as to why the series is needed (if it is not obvious)
- How the series achieves your goal
- It should list any pre-conditions and major assumptions you have made
- It should refer to any specifications, design documents, previous discussion on mailing lists and other relevant information
The amount of detail required depends on the complexity and size of the patch series. The larger and more complex the series, the more information is required. The goal of the information is to make it easier for the code reviewer to understand your series. The more time you invest in preparing the series' cover letter, the easier it will be for a reviewer to understand your code.
However, cover letters do not get committed to the git tree: if the cover letter contains information that should be in the git tree, you may want to create a new document under docs/designs, docs/features or docs/specs instead as part of the series and refer to it from the series.
Change log (for patch series revisions >= 2)
The end of the cover letter is also the location where you would typically track changes between different versions of the patch series. The format is identical to change logs of individual patches (see here), but a series change log is much less detailed and more high-level than for a patch. The key purpose is to point reviewers to areas of the series which need to be revisited.
Providing a git branch
If you send a large patch series, it is recommended to include a branch in your public git repository in your cover letter, so that reviewers can pull directly from that branch.
If you do not have a public repository, you can fork the Xen Project's GitHub or GitLab mirrors at https://github.com/xen-project/xen and https://gitlab.com/xen-project/xen into your own project space and push your branch to your own fork and provide a link to that branch. If you are a regular contributor to the Xen Project, you can request to host personal repositories at xenbits by sending an email to community dot manager at xenproject dot org.
Sending the patches to the list
The xen-devel mailing list is moderated for non-subscribers. It is not mandatory to subscribe but it can help avoid this delay. It is possible to subscribe and then disable delivery in the mailman options so as to avoid moderation but not receive list traffic if that is what you would prefer.
Setting up git send-email
The most robust way to send files is by using the git send-email command. (If you're using mercurial, please see our Submitting_Xen_Patches_-_mercurial).
To do this, first set configure your information:
git config --global sendemail.from "YOUR NAME <email@example.com>"
git config --global sendemail.smtpserver imap.example.org
git config --global sendemail.smtpuser USER
# depending on your config you may also set:
git config --global sendemail.smtpencryption tls
If you don't want to enter password for your SMTP server all the time:
git config --global sendemail.smtppass = PASS
Settings that help save you time
There are a number of settings you may want to set globally or per repository, such as
# Allows you to drop --thread from git format-patch ...
git config --global format.thread true
# Allows you to use -s or --signoff when committing a patch
git config --global user.name "YOUR NAME"
git config --global user.email "<firstname.lastname@example.com>"
Subject Prefix
Patches and patch series are posted to a mailing list: when using the
git format-patch command a subject prefix is added to a patch or patch series, which helps disambiguate normal discussions from posted patches and code reviews.
git format-patch creates mails with subject lines such as
# Single patch
[<SUBJECT-PREFIX>] <Title of patch in git>
# Patch series
[<SUBJECT-PREFIX> 0/n] <Title of cover letter/patch series>
[<SUBJECT-PREFIX> 1/n] <Title of 1st patch in git>
[<SUBJECT-PREFIX> n/n] <Title of nth patch in git>
Canonical Subject Prefix
As patches for different git repositories can be posted (or CC'ed) to different mailing lists, some conventions have emerged over time which help code reviewers identify which patch is intended for which git tree. We refer to these as canonical subject prefix. The table below shows recommended default Subject Prefixes, which either
- need to be passed using the
--subject-prefix=<Subject-Prefix>option when calling
git format-patch,
- or can be set as defaults per git repository as described here
The following table lists common canonical subject prefixes used in the project
|Subject Prefix
|git default
XEN PATCH (recommended)
MINI-OS PATCH (recommended)
|minios-devel@ but sometimes xen-devel@ is CC'ed
IMPORTANT: If you do not use a canonical subject prefix some existing and future automated tooling may not work correctly: consider for example a situation in which a patch for livepatch-build-tools.git is sent to xen-devel@ and that this triggers a build test in different environments. In this case, the build test would try and apply the patch to xen.git and might fail in unexpected ways.
Common modifications to the Subject Prefix
In addition, the following modifications to Subject Prefixes are commonly used and can also be used in combination
|Subject Prefix Modification
|When to use
|RFC means "Request For Comments"; use this when sending an experimental patch for discussion rather than application.
|Typically used if your patch has not been reviewed for some time and you want to remind people of the patch
... for-<release>
XEN PATCH for-4.13
|Typically used after the master xen.git branch has been feature frozen and you want to highlight a patch that is destined for the release which is currently being developed
... for-next
XEN PATCH for-next
|Typically used towards the end of a development cycle when you want to highlight a patch that is destined for the next release
git format-patch contains options to help with these
--rfcwill mark a patch as RFC, but will always lead to
--subject-prefix=<Subject-Prefix>allows you to set a subject prefix, but will overwrite any defaults you may have set
Changing git defaults to use the Canonical Subject Prefix
To change the setting perform
cd <local-git-tree>
git config --local format.subjectPrefix "<canonical subject prefix>"
Sending a Patch Series
Step 1: Create patches using git format-patch
Git format patch allows you to create and save formatted patches in a directory. By default it will create them in the root of your git directory, but you probably want to direct this into a
../patches/feature-version directory (in the examples below
../patches/feature-v2 would contain only v2 of that series). It is also possible to store several versions of a patch, e.g. v1, v2, etc in the same
../patches/feature directory). Let's say the last two commits of your head are part of your series you want to send out. In this case, the command line would look like
$ git format-patch --reroll-count=2 --thread --cover-letter -o ../patches/feature-v2 -2
This will create 3 files, such as
v2-0000-cover-letter.patch v2-0002-Patch-to-do-bar.patch v2-0001-Patch-to-do-foo.patch
- You will need to edit the subject and body of
- You must always use the --thread and --cover-letter options. If you omit --thread, any automatic tooling and patch checking that is triggered by sending a mail to one of our mailing lists may not work without using this option. You can set --thread as a default, as outlined here.
Other useful options include:
--subject-prefix=Subject-Prefix: please read this document before using these options
Step 2: Use add_maintainers.pl (or get_maintainer.pl)
Option 1: use add_maintainers.pl
$ ./scripts/add_maintainers.pl -d ../patches/feature-v2
Then follow the instructions (which are essentially Step 3, with correct command line options based on what you pass to
add_maintainers.pl). Note that the
add_maintainers.pl script works around a limitation of
git send-email ... --cc-cmd="./scripts/get_maintainer.pl" ..., which does not automatically update the CC list of your cover letter.
Other useful options include:
-v 2): If you store your patches in one directory with different versions in it generated by
--reroll-count=2you want to use this option
--patchcc|-p LOCATION: Inserts CC's into a specific location (see
--help) to *.patch files
--covercc|-c LOCATION: Inserts CC's into a specific location (see
--help) to the cover letter
--tags|-t: Adds people who have *-by tags to the mail header (
git send-emaildoes not do this itself)
--tagscc: Adds people who have *-by tags to the CC list
-a "<argument1 with space>" -a <argument2> ...for arguments you want to pass to
Common LOCATION combinations include:
-p commit: copy CC blocks into the *.patch body (CC's will become part of the commit message)
-p none -c header: copy CC blocks from *.patch files in the cover letter without modifying *.patch files. This is useful in rerolled patches, where you do not want to modify the CC blocks.
-p ccbodybehaves similarly, only that any new CCs that may come from an updated MAINTAINERS file or from new files that have been added to *.patch files will be added to *.patch files.
-p comment -c end: copy CC blocks after the *.patch body (CC's will not be committed) and into the body of the cover letter
Option 2: use get_maintainer.pl manually
Foreach <v2 patchfile> in ../patches/feature (with XXXX > 0000): - Run: ./scripts/get_maintainer.pl <v2 patchfile> - Review the e-mail list and prefix each line with Cc: - Copy the e-mail CC block into patchfile - Do anything else you want to do manually For v2-0000-cover-letter.patch take the superset of all the files generated previously and merge, then copy the e-mail CC block into 0000-cover-letter.patch
Step 3: Send patches using git send-email
Send the patches using
$ git send-email --to firstname.lastname@example.com ../patches/feature-v2/*.patch
Other useful options include:
--ccif you need to CC additional reviewers (e.g. from within your team)
Submitting patches against point releases, such as Xen 4.10
When you develop against older Xen versions you are likely going to use an outdated version of the MAINTAINERS file. Typically only the files on staging or master are up-to-date. To work around this, use the following slightly modified workflow
$ git format-patch ... -o <patchdir> ...
$ checkout master
$ ./scripts/add_maintainers.pl -d <patchdir>
$ checkout <original branch>
$ git send-email ... <patchdir>
This ensures that you use the latest set of tools and the latest MAINTAINERS file
Sending an individual patch
You can use the same workflow as outlined in the previous section, without generating a cover letter. In this case, the
git-format-patch command line in step 1 would look like
$ git format-patch --thread -o ../patches/bugfix-v2 -1
This is followed by steps 2 and 3. However, for single patches without a cover letter, using
git-send-email alone, is quite a reasonable option. In this case, you can use the following command line, which will get the CC list from the
./scripts/get_maintainer.pl script, which allows you to fold all 3 steps into 1.
$ git send-email --to email@example.com --cc-cmd="./scripts/get_maintainer.pl" -1
Other useful options include:
--dry-runwill go through all the motions of preparing the patchbomb, but instead of sending a mail, will just output the mails it would have sent. Useful for testing.
--ccif you need to CC additional reviewers (e.g. from within your team)
--reroll-count=Nallows you to change the revision of the patch
--subject-prefix=Subject-Prefixallow you to change the subject prefix: please read this document before using these options
Using add_maintainers.pl (or get_maintainer.pl) from outside of xen.git
You can use
add_maintainers.pl or
get_maintainer.pl on any Xen Project git repository with a compatible
MAINTAINERS file in the root of its tree. An example is
livepatch-build-tools.git. In this case simply replace
./scripts/add_maintainers.pl or
./scripts/get_maintainer.pl with the full path to the script.
# You are in the xen.git sister repository (e.g. livepatch-build-tools)
$ git format-patch ... -o <patchdir> ...
$ $LOCATION-OF-XEN-GIT/scripts/add_maintainers.pl -d <patchdir>
$ git send-email ... <patchdir>
A minimum template for such a
MAINTAINERS file can be found below.
This file follows the same conventions as outlined in
xen.git:MAINTAINERS. Please refer to the file in xen.git
for more information.
M: MAINTAINER1 <firstname.lastname@example.com>
M: MAINTAINER2 <email@example.com>
L: firstname.lastname@example.com
S: Supported
V: xen-maintainers-1
Review, Rinse & Repeat
After posting your patches you will hopefully see some response in the form of comments, patch review and eventually commit.
Code Review
The form of the review may often be quite direct and to the point which may be daunting for some people. However bear in mind that detailed criticism of a patch usually means that the reviewer is interested in your patch and wants to see it go in!
Once you have addressed any review you should normally resend the patch. It is normally expected that you address all review comments before reposting. This often means code changes in your patch but could also mean simply responding to the review comments explaining you reasoning or giving reasons why something should be the way it is.
You should also rebase your change against the project's development tree before sending out a new version, such that when it is approved it applies cleanly. The only reason not to do that is if you don't expect it to be approved, and want feedback on what you have. In that case you can do the rebase later.
The relevant command line options in
./scripts/add_maintainers.pl and
git-send-email (if used standalone) for reposting new revisions is
Highlight changes in the new version
When resending a patch you should normally include a note of the changes between the current and last version of the patch. Common practice is to include these notes after your Signed-off-by separated by a triple-dash (
---). This indicates patch commentary specific to the posting which need not be included in the final changelog (although you should also remember to update the changelog if necessary). You should also include a "V2" (V3, V4 etc) tag in the subject line (if you are using the git
send-email command then the
--reroll-count=N option is helpful here, or for older git versions
--subject-prefix='PATCH vN').
If someone replies to your patch with a tag of the form Acked-by: <Developer>, Reviewed-by:, Tested-by: etc then, assuming you have not significantly reworked the patch, you should include these tags in any reposting after your own Signed-off-by line. This lets people know that the patch has been seen and that someone approves of it and also serves to prevent reviewers wasting time re-reviewing a patch which is not significantly different to last time. The developers with commit access also like to see postings with such tags since it means they are likely to be much easier to deal with and commit.
An example of a new Patch Version
An example of a resend of the example patch from above might be:
Subject: [PATCH v2] foobar: Add a new trondle calls
Add a some new trondle calls to the foobar interface to support
the new zot feature.
Signed-off-by: Joe Smith <email@example.com>
Acked-by: Jane Doe <firstname.lastname@example.com>
Changed since v1:
* fix coding style
* be sure to treadle the trondle in the error case.
diff -r 63531e640828 tools/libxc/Makefile
--- a/tools/libxc/Makefile Mon Dec 07 17:01:11 2009 +0000
+++ b/tools/libxc/Makefile Mon Dec 21 11:45:00 2009 +0000
Resending Patches
If you do not get any response to your patch or you got lots of Acked-by's but the patch has not been committed (remember that reviewers and maintainers are busy people too and sometimes things may fall through the cracks) then after some time, perhaps 2-4 weeks (guidelines), you should resend the patch, perhaps including [RESEND] in the subject line to alert people that the last mail was dropped. Before resending you should:
- Check that the patch has not been applied to the staging branch, since committers do not always send a notification when they apply a patch.
- Consider if there is anything you can do to improve the commit message or subject line of your patch to better attract the attention of the relevant people.
Remember to include any Acked-by/Reviewed-by which you received in response to the previous post.
How to know when a patch has been committed
Changes committed to Xen Project by the committers are immediately available in the "staging" branch of the main xen.git tree. They are then automatically tested, and if the tests pass the changes are propagated to the "master" branch.
After your patch is committed
If your patch turns out to break something you will be expected to respond promptly to help diagnose and fix the problem. This assumes that you in particular keep an eye on the osstest flight reports sent to xen-devel. If it can't be fixed quickly, your change may be reverted.
How to Generate and Submit a Patch to Qemu-Xen
Xen Project uses QEMU as device model, that is the software component that takes care of emulating devices (like the network card) for HVM guests. Two QEMU trees, both using git for revision control, are currently in use by xen.git:
- qemu-xen-traditional: old and stable tree, only bug fixes are accepted in this tree at the moment;
- qemu-xen: new tree used for development, based on the latest stable branch of Upstream QEMU, that currently is available at qemu git repo. See QEMU Upstream on how to manually build it and use it to run VMs.
New features should be developed again the latest upstream QEMU first, see http://wiki.qemu.org/Contribute/SubmitAPatch, then upon request they can be backported to qemu-xen. Only patches that have been acked and committed to qemu.git are eligible to be backported to qemu-xen. In order to request a backport, send an email to email@example.com, specifying the original commit id in qemu.git and the reason why the patch should be backported to qemu-xen.
How to Generate and Submit a Xen Project Patch to the Linux Tree
Like Xen Project, Linux uses the git SCM. The Linux tree contains documentation on submitting patches, in Documentation/SubmittingPatches, as well as a script (scripts/checkpatch.pl) that ensures your patch is in Linux house style. Running git apply --check on your patch can reveal merge errors.
Patches should be emailed to firstname.lastname@example.com, email@example.com, and any relevant Linux maintainers (which can be found by running scripts/get_maintainer.pl on your patch).
The FreeBSD project uses svn for it's master source tree, although git clones are also available. Checkout the code from either the svn or git mirror and remember to always create your patch against the HEAD branch. It can be backported to stable versions afterwards, but it needs to be initially committed to HEAD.
The best way to get your patches reviewed is to use Phabricator and assign them to the relevant maintainer (check MAINTAINERS in the source tree), for Xen related code that would be royger.
How to Generate and Submit a Xen Project Patch to MiniOS and Unikraft
MiniOS uses the following git tree for development: mini-os.git. Patches are submitted to minios-devel@.
Unikraft uses several git trees under the unikraft namespace for development: unikraft/. Patches are submitted to minios-devel@ and are marked with a UNIKRAFT prefix (or with a library name prefix), such that they can be differentiated from MiniOS patches. A detailed description of the Unikraft convention can be found in the Unikraft base repository unikraft/unikraft.git: CONTRIBUTING.md.


text:
Patch 5.4.1 Live This Week
Patch 5.4.1 goes live this week, bringing updates to the Recruit a Friend system, the Blizzcon pet, and tooltip updates to reflect the Patch 5.4 hotfixes. The previously mentioned merging of all previous patches into one file has been reverted, so it should be a very small download.
Murkalot's Flail is the Blizzcon Reward pet added in Patch 5.4.1, and grants the Murkalot achievement. If you aren't going to Blizzcon, you can still get him by purchasing the Virtual Ticket.
Recruit a Friend In-Game UI
The Recruit a Friend system has been moved in game, making it even easier to use.
Emerald Hippogryph
The Emerald Hippogryph is the new Recruit a Friend reward and grants the Friends In Places Even Higher Than That achievement.
Recruit a Friend Pet Rewards
Some pets that were previously only used for promotions in Asia are now Recruit a Friend rewards.
Achievement Changes
Originally Posted by MMO-ChampionArena
Player vs. Player
- Are You Not Entertained? no longer rewards 10 points
Feats of Strength
- Friends In Places Even Higher Than That (New) Obtain an Emerald Hippogryph mount through the Recruit-a-Friend program. Account Wide.
- Murkalot (New) Proud owner of Murkalot from the 2013 BlizzCon. Account Wide.
Player vs. Player
- Fire-Watcher has been updated to reflect the hotfix down to 2,000 coins, down from 10,000.
Proving Grounds
- You're Doing it Wrong now rewards 10 points.
Mounts and Pets
Originally Posted by MMO-ChampionMounts
- Emerald Hippogryph (New) Summons and dismisses a rideable Emerald Hippogryph. The capabilities of this mount depend on your Riding skill and location. Account wide. 1.5 sec cast.
- Bernard (New) Right Click to summon and dismiss Bernard. Battle Pet. Instant.
- Murkalot (New) Right Click to summon and dismiss Murkalot. Battle Pet. Instant.
New Strings
Originally Posted by MMO-Champion
- BLIZZARD_STORE_ERROR_PARENTAL_CONTROLS - Feature has been disabled by Parental Controls.
- CHOOSE_ONE_REWARD - Choose 1 Reward
- CLAIM_REWARD - Claim Reward
- ERR_RECRUIT_A_FRIEND_ACCOUNT_LIMIT - You have submitted the maximum number of recruits for this time period. Please try again later.
- ERR_RECRUIT_A_FRIEND_FAILED - Failed to send Recruit A Friend request. Please try again later.
- PREVIEW - Preview
- PRODUCT_CHOICE_NO_TAKE_BACKSIES - Are you sure? You can't change your selection after this step.
- PRODUCT_CHOICE_SUBTEXT - (%s)
- PRODUCT_CLAIMING_FAILED - Error claiming product. Please try again.
- QUEUED_STATUS_LOCKED - |cffff2020Locked|r
- QUEUED_STATUS_LOCKED_EXPLANATION - You are locked to this rated battleground until it finishes.
- RAF_BENEFIT1 - Level Faster
- RAF_BENEFIT2 - Grantable Levels
- RAF_BENEFIT3 - Summon your friend
- RAF_BENEFIT4 - 30 days of free game time
- RAF_BENEFIT5 - In-Game Mount
- RAF_BENEFITS - Benefits
- RAF_BUTTON_DISABLED_FACTION - You cannot use Recruit A Friend while playing a neutral character.
- RAF_BUTTON_REWARD_TOOLTIP_DESCRIPTION - You have earned a reward from Recruit A Friend! Click here to claim it!
- RAF_BUTTON_REWARD_TOOLTIP_TITLE - Recruit A Friend Reward
- RAF_BUTTON_TOOLTIP_DESCRIPTION - You can recruit a friend and earn fantastic rewards!
- RAF_BUTTON_TOOLTIP_TITLE - Recruit A Friend
- RAF_DESCRIPTION - Earn game time, in-game rewards,\nand more by recruiting your friends
- RAF_ENTER_EMAIL - Enter your friend's email address
- RAF_ENTER_NOTE - Write a note to your friend
- RAF_ENTER_NOTE_PROMPT - Enter a note...
- RAF_FAQ - Recruit a Friend FAQ
- RAF_INVITATION_SENT - Your invitation has been sent!\n\nYour friend will receive an email with instructions on creating a new account and downloading the game. You will be notified in-game when they have created a new character and you can begin your adventure together.
- RAF_INVITEE_FRIEND_ADDED_EXPLANATION - You are now friends with the person who invited you to play World of Warcraft.\n\n|cffffd200Right-click|r their name to whisper them when they are online.\n\nYou can now join up and enjoy Azeroth together!
- RAF_INVITEE_FRIEND_ADDED_NOTICE - Open your friends list to find your friend that invited you to play World of Warcraft
- RAF_INVITER_FRIEND_ADDED - Your recruited friend is now your Battletag Friend: |cff88C5ff[%s]|r
- RAF_MORE_DETAILS - [Click here for more details on how it works.]
- RAF_PRODUCT_CHOICE_CLAIM - Click to choose your reward
- RAF_PRODUCT_CHOICE_EARNED - You have earned a Recruit A Friend Reward
- RAF_REALM_INFO - Your friend will be directed to join:\n|cffffd200%1$s|r on |W|cffffd200%2$s|r|w
- RAF_SEND_INVITATION - Send Invitation
- RECRUIT_A_FRIEND - Recruit A Friend
- RECRUIT_A_FRIEND_FACTION_SUGGESTION_ALLIANCE - Your friend plays for the Alliance faction. Pick one of these races if you want to play together.\n\nHuman, Dwarf, Night Elf, Gnome, Draenei, Worgen, or Pandaren
- RECRUIT_A_FRIEND_FACTION_SUGGESTION_HORDE - Your friend plays for the Horde faction. Pick one of these races if you want to play together.\n\nOrc, Undead, Tauren, Troll, Blood Elf, Goblin, or Pandaren.
- RECRUIT_A_FRIEND_REWARDS - Recruit A Friend Rewards
New Mail
Originally Posted by MMO-ChampionAutomated In-game Mail
- Automated In-game Mail #399 - Emerald Hippogryph: Some feel that the Emerald Hippogryph is the most majestic of these noble creatures.
Even if one does not agree, they are certainly a striking sight nonetheless!
--Mei Francis - Exotic Mounts
New Icons
Recruit-A-Friend Updates Coming Soon
Connected Realms Update
Blue Posts
Originally Posted by Blizzard Entertainment
News Recap
There has finally been some news recently, so here is your chance to catch up!
- October 17
- Blizzard All-Stars was renamed to Heroes of the Storm
- The BlizzCon 2013 Map and Schedule were released!
- October 18
- Paragon posted their video of the solo healed Heroic Garrosh 10 encounter.
- October 20
- We looked at the overall raid completion rate of players.
- October 22
- Holinka shared some information about how the new region wide arena pools and new mounts are working out
- October 24
- Reaper of Souls will be bringing back the Mystic that was removed from beta, adding Transmogrification and Enchanting (similar to Reforging in WoW).
- October 25
- The contents of the Blizzcon goody bag were released.
- October 27
- We looked at a partially complete implementation of character level scaling that was added in Patch 5.4.

subset: commoncrawl


text:
Top Items:
Wall Street Journal:
Microsoft Is in Talks To Buy Facebook Stake — SAN FRANCISCO — Microsoft Corp. is in talks with Facebook Inc. about making an investment in the social-networking startup that could value Facebook at $10 billion or more, according to people familiar with the matter.
Discussion: PDA, Business Week, Bits, Webware.com, 24/7 Wall St., CenterNetworks, TechCrunch, Read/WriteWeb, VentureBeat, paidContent.org, IP Democracy, Andy Beal's Marketing Pilgrim, Silicon Alley Insider, Digital Daily, HipMojo.com, Valleywag, Tech Trader Daily, A VC, Inside Facebook, Search Engine Land, Jeremy Toeman's LIVEdigitally, One By One Media, FaceReviews.com, Greg Galitzine's VoIP …, IP Telephony, VoIP, Broadband, Scobleizer and Clickety Clack
Jemima Kiss / PDA: Microsoft and Google vie for share of Facebook
Caroline McCarthy / Webware.com: REPORT: MICROSOFT PLANS TO INVEST IN, NOT ACQUIRE, FACEBOOK
Allen Stern / CenterNetworks: Microsoft Looking to Buy 5% of Facebook
Michael Arrington / TechCrunch: Microsoft May Invest in Facebook At $10 Billion Valuation
Staci D. Kramer / paidContent.org: Microsoft Negotiating For Equity Stake In Facebook: Report
Cynthia Brumfield / IP Democracy: Is Facebook Worth $10 Billion?
Jordan McCollum / Andy Beal's Marketing Pilgrim: Rumor Mill: Microsoft Buying a Stake in Facebook
John Paczkowski / Digital Daily: Megalomaniabook … Guess Facebook CEO Mark Zuckerberg …
Ashkan Karbasfrooshan / HipMojo.com: MSFT/Facebook Rumor Creeps Back Up Again: Will it Help or Hurt Facebook?
Eric Savitz / Tech Trader Daily: Here's To You, Peter Thiel
Justin Smith / Inside Facebook: Microsoft, Google want a piece of Facebook
Barry Schwartz / Search Engine Land: Microsoft May Buy 5% Stake In Facebook
Jeremy Toeman / Jeremy Toeman's LIVEdigitally: Unsubstantiated rumor floods blogosphere
Rodney Rumford / FaceReviews.com: Microsoft and Facebook Business Connection Strengthens
Russell Shaw / IP Telephony, VoIP, Broadband: Poll: With Microsoft now talking to Facebook, who should buy them?
Robert Scoble / Scobleizer: Microsoft may buy part of Facebook
Junior Hines / Clickety Clack: Microsoft Wants To Buy A Piece Of Facebook
Mathew / mathewingram.com/work:
Will MSFT push Yahoo to buy Facebook? — According to the Wall Street Journal, the software behemoth known as the Beast from Redmond is looking at buying between three and five per cent of Facebook for between $300-million and $500-million. As any math whiz (of which I am not one) …
Discussion: Groundswell
Charlene Li / Groundswell: Facebook - is it worth $10 billion?
Larry Dignan / Between the Lines:
Microsoft reportedly eyeing Facebook stake — Microsoft is eyeing an investment in Facebook that would value the social networking company at about $10 billion. — The investment, which was reported by The Wall Street Journal citing "people familiar with the matter, connects a few dots on the social networking landscape.
Discussion: InfoWorld, alarm:clock and Searchviews
Juan Carlos Perez / InfoWorld: Report: Microsoft seeks Facebook stake
Sepideh Saremi / Searchviews: Google Weekend: Open API, Social Media, and Unity Cable Rumors
Om Malik / GigaOM:
Microsoft Wants A Piece Of Facebook?
Microsoft Wants A Piece Of Facebook?
Discussion: Logic+Emotion
Microsoft in talks to invest in Facebook: report
Microsoft in talks to invest in Facebook: report
Discussion: Business Week and rexblog.com
Rob Hof / Business Week: Facebook Still Dancing for Dollars
Rex Hammock / rexblog.com: MS's 5% stake in FB vs. GOOG's 5% stake in AOL
PR Newswire:
Apple today released the following statement: — CUPERTINO, Calif. /PRNewswire-FirstCall/ — Apple has discovered that many of the unauthorized iPhone unlocking programs available on the Internet cause irreparable damage to the iPhone's software, which will likely result …
Adrian Kingsley-Hughes / Hardware 2.0: End of the road for unlocked iPhones
Ilya Kochanov / CrunchGear: Apple: Stop Unlocking iPhones. Please?
Darren Murph / Engadget: Apple finally weighs in on iPhone hacks, unlocking
Dennis Sellers / Macsimum News: Digital music 'Now Playing' at Starbucks
Russell Shaw / IP Telephony, VoIP, Broadband: Hey there's an iPhone firmware update this week: if you are running …
Larry Dignan / Between the Lines:
Apple to nuke unlocked iPhones with next update — Apple is playing hardball with the unlocked iPhone movement. — In a terse statement, Apple said "many of the unauthorized iPhone unlocking programs available on the Internet cause irreparable damage to the iPhone's software …
Discussion: Christopher Null and Digital Daily
John Paczkowski / Digital Daily: New Use for $100 iPhone Credit: Replace Inoperable iPhone
Jacqui Cheng / Ars Technica:
Apple: firmware update likely to make unlocked iPhones "permanently inoperable"
Apple: firmware update likely to make unlocked iPhones "permanently inoperable"
Discussion: Gizmodo
Associated Press:
Apple warns hacking iPhone may harm it
Apple warns hacking iPhone may harm it
Discussion: MobHappy
Carlo Longino / MobHappy: Apple Issues A Not-So-Veiled Threat About Unlocking the iPhone
Benwilson / iPhone Atlas:
Apple reps: iPhone warranty will be voided by hacks (third-party native apps)
Apple reps: iPhone warranty will be voided by hacks (third-party native apps)
Discussion: Mashable! and One More Thing
Kristen Nicole / Mashable!: iPhone Apps Can Void your Apple Warranty
Duncan Martell / Reuters:
Apple says unlocking software can damage iPhone
Apple says unlocking software can damage iPhone
Discussion: mocoNews.net
Brandon LeBlanc / The Windows Experience Blog:
Experiencing Windows Vista Service Pack 1 Beta — Today Microsoft is releasing the Beta of Windows Vista Service Pack 1 which was announced by Nick White few weeks ago. I'd like to take the opportunity to share my very own experiences with Windows Vista SP1 Beta running on several PCs of my own.
Discussion: InfoWorld, Download Squad, Engadget, Channel 9, BetaNews, Bink.nu, WinBeta and GottaBeMobile.com
Nancy Gohring / InfoWorld: Microsoft releases SP1 beta to limited group
Darren Murph / Engadget: Microsoft beams out Vista SP1 to beta testers
Keeron / Channel 9: Vista SP1 beta release today
Steven Bink / Bink.nu: Windows Vista SP1 Beta release available today
Warner Crocker / GottaBeMobile.com: Vista SP1 Now In Wider Release For Beta Testing
Louise Story / New York Times:
Company Will Monitor Phone Calls to Tailor Ads — Companies like Google scan their e-mail users' in-boxes to deliver ads related to those messages. Will people be as willing to let a company listen in on their phone conversations to do the same? — Pudding Media, a start-up based in San Jose …
Discussion: Pudding Media, Business Week, GigaOM, Insider Chatter, Epicenter, Associated Press, Download Squad, Digital Daily, Bruce Clay, Inc. Blog, Search Engine Land, TechBlog, Valleywag, Good Morning Silicon Valley, alarm:clock, MediaBytes with Shelly …, michael parekh on IT, p2pnet, Alec Saunders .LOG, VoIP & Gadgets Blog, dailywireless.org, BloggingStocks and dslreports.com
Om Malik / GigaOM: The Mad Ad World & Cheap Calls
Terrence Russell / Epicenter: Pudding Media Raises Privacy Concerns by Monitoring VoIP Calls
Peter Svensson / Associated Press: New service eavesdrops on Internet calls
John Paczkowski / Digital Daily: Guess 'Puddin' Head Media' Was Already Trademarked, Huh?
Lisa Barone / Bruce Clay, Inc. Blog: Pudding Is Delicious, Eavesdropping Is Not
John Murrell / Good Morning Silicon Valley: ThePudding? More like Wiretapioca
Shelly Palmer / MediaBytes with Shelly Palmer Video: MediaBytes - 09.24.07 — Click to view today's MediaBytes video.
Karl / dslreports.com: 'The Pudding' Listens In On VoIP - And displays context-sensitive advertisements...
Henry Blodget / Silicon Alley Insider:
Today's Terrible Idea: Pudding Media
Today's Terrible Idea: Pudding Media
Discussion: VentureBeat, IP Democracy, 901am, AppScout, TechCrunch, Webware.com, ExtremeTech, Life On the Wicked Stage, WebProNews and Clickety Clack
Cynthia Brumfield / IP Democracy: Just Say No to Pudding Media — In what Henry Blodget deems …
Dennis Bouchand / 901am: Pudding Media delivers free calling by delivering fun, entertaining …
Mark Hachman / AppScout: Would You Like Advertisers Listening to Your Calls?
Mark Hendrickson / TechCrunch: ThePudding: Targeted Advertising Comes to Phone Calls
Erica Ogg / Webware.com: THE PUDDING: EAVESDROPPING TO SELL YOU STUFF
Joel Durham Jr / ExtremeTech: Ad Software Listens In to Internet Phone Calls
Warner Crocker / Life On the Wicked Stage: Phone Eavesdropping Service To Help Target Ads?
Jason Lee Miller / WebProNews: The Privacy Is In The Pudding (Or Not)
Junior Hines / Clickety Clack: Algorithms Grab The Spotlight
Ted / Ted's Take:
"PayPal Meets MasterCard" Without The High Fees — MEDIA CONTACT: — Brad Burns — 202-776-1400 — firstname.lastname@example.com — REVOLUTION JOINED BY INDUSTRY LEGENDS AND MAJOR BANKS TO LAUNCH REVOLUTIONARY PAYMENT SYSTEM — Steve Case, Ted Leonsis, Larry Summers, David Pottruck …
Discussion: Read/WriteWeb, Life On the Wicked Stage and paidContent.org
Marshall Kirkpatrick / Read/WriteWeb: Revolution Money to Take on PayPal, the World
Warner Crocker / Life On the Wicked Stage: Could This Be A Game Changer For the MoneyChangers?
Joseph Weisenthal / paidContent.org: Steve Case, Ted Leonsis Launch Online Credit-Card Firm Revolution …
Jonathan Fildes / BBC:
'$100 laptop' to sell to public — Computer enthusiasts in the developed world will soon be able to get their hands on the so-called "$100 laptop". — The organisation behind the project has launched the "give one, get one" scheme that will allow US residents to purchase two laptops for $399 (£198).
Discussion: Read/WriteWeb, The Browser, Cinema Blend Feeds, Wikinomics, Daggle and broadstuff
Josh Catone / Read/WriteWeb: Selling OLPC Laptops in USA - Good Idea?
Oliverryan / The Browser: A better alternative to One Laptop per Child?
Dan Herman / Wikinomics: Tech solutions to under-development.
Danny Sullivan / Daggle: $100 Laptop? Don't Wait — Get Yours Now
Steve Lohr / New York Times:
Buy a Laptop for a Child, Get Another Laptop Free
Buy a Laptop for a Child, Get Another Laptop Free
John Murrell / Good Morning Silicon Valley: One Laptop Per Child issues pitch to fix slow boot sequence
Marius Chitosca / Smart Mobs: "Buy a Laptop for a Child" Project going steady
Linda Tischler / Fast Company Now: One Laptop Per Child: Failure is not an Option
Jessica E. Vascellaro / Wall Street Journal: Laptop Charity Seeks Help From Home Market
Carolyn Y. Johnson / Boston Globe: Building a critical mass
Nick Mokey / Digital Trends: OLPC XO-1 Goes On Sale to Public
Scott Gilbertson / Compiler: OLPC Laptops Available In The U.S. With "Give One Get One" Program
Official Google Blog:
It's all about today — A lot of us love video games, and everyone here has their favorite from the latest generation of consoles. We have a game room in our building that happens to have all three of the latest systems: Artem loves Microsoft's Xbox 360, Niv can't part with Sony's Playstation 3 …
Discussion: Search Engine Journal, Google Operating System and Mashable!
Loren Baker / Search Engine Journal: Google Trends Now Updates Daily
Ionut Alex Chitu / Google Operating System: Google Trends, Updated Daily
Adam Ostrow / Mashable!: Google Trends Now Updates Daily
Prince McLean / AppleInsider:
Updated Leopard requirements to exclude 800MHz systems — Just weeks ahead of its public launch, Apple Inc. has updated the minimum system requirements for its next-generation Leopard operating system to exclude 800MHz PowerPC-based Macs, AppleInsider has learned.
Discussion: Infinite Loop, Byte of the Apple, Compiler, Gizmodo, CrunchGear, The Unofficial Apple Weblog and Ubergizmo
Arik Hesseldahl / Byte of the Apple: So Long PowerPC — It had to happen sometime, and it looks …
Scott Gilbertson / Compiler: Rumor: OS X Leopard Nears Completion
Wilson Rothman / Gizmodo: Apple: 800MHz G4 Macs Are Dead to Leopard
Vince Veneziani / CrunchGear: Leopard To Exclude Legacy Apple Systems?
Dave Caolo / The Unofficial Apple Weblog: Leopard to exclude 800MHz systems
Robert Scoble / Scobleizer:
Is FeedHub the answer to information overload? — I've been playing with mSpoke's FeedHub, releasing today at the Demo Conference. I'll have a video up later today demonstrating the product. — Dan Farber has a review and info up on his ZDNet blog. — I've been interested i this topic for some time.
Discussion: Profy.Com, Read/WriteWeb, Between the Lines, Chuqui 3.0.1 Beta and Somewhat Frank
Phil Butler / Profy.Com: DEMOfall 07 Presents: Feedhub - One Cure for Online ADD
Richard MacManus / Read/WriteWeb: FeedHub Launches - Individualized RSS Feeds
Frank Gruber / Somewhat Frank: FeedHub Personalized Feed Creator
Brad Stone / NYT:
New York State Investigates Facebook — Another state attorney general is getting tough with Facebook. — In the wake of scrutiny of the hot social network by Attorney General Richard Blumenthal of Connecticut, his New York state counterpart, Andrew M. Cuomo, has subpoenaed Facebook asking …
Juan Carlos Perez / InfoWorld: NY blasts Facebook over predators, subpoenas docs
Adam Ostrow / Mashable!: Facebook Investigated for Safety Practices
Tony Smith / The Register:
Apple iPhone — Personal view We've already reviewed Apple's iPhone, so why are we taking another look? There are several reasons. First, a different reviewer means a different opinion. That applies to any product, of course, but Apple's claim that the iPhone is "revolutionary" perhaps justifies an alternative appraisal.
Discussion: PalmAddicts
Sam Mcloughln / PalmAddicts: Register Reviews the iPhone - Again
Astrid Wendlandt / Reuters:
Vivendi calls Apple iTunes contract terms "indecent" — PARIS (Reuters) - Vivendi condemned as "indecent" the contract terms between its Universal Music Group (UMG) unit and Apple Inc, the computer maker whose iTunes online store dominates the digital music market.
Discussion: Engadget, Infinite Loop, Digital Daily, Silicon Alley Insider and The Unofficial Apple Weblog
Donald Melanson / Engadget: CE-Oh no he didn't! Part XLIII: Vivendi CEO calls iTunes contract "indecent"
John Paczkowski / Digital Daily: FCC Swamped With iTunes Indecency Complaints
Peter Kafka / Silicon Alley Insider: Vivendi: Apple's iTunes Terms Are Terrible!
Scott McNulty / The Unofficial Apple Weblog: Vivendi wants bigger cut of iTunes pie
Microsoft Corporation:
Windows Server 2008 Release Candidate Evaluation — Note: Windows Server 2008 Release Candidate 0 will be available here shortly. — Click an option below to continue, or to read all of the option descriptions at one time, select the View all descriptions check box. — View all descriptions
Discussion: InfoWorld, WinBeta, Bink.nu and TechSpot News


text:
Acute graft-versus-host disease
What every physician needs to know about acute graft-versus-host disease:
Acute graft-versus-host-disease (acute GVHD) occurs when lymphocytes from another person are able to survive and proliferate in a patient; it is one of the most serious complications of allogeneic bone marrow transplantation (BMT).
Rare causes of acute GVHD include maternal transfer of lymphocytes via the placenta to an immunodeficient infant, and transfusion of non-irradiated blood to a patient whose immune system cannot reject the donor lymphocytes, either due to immunodeficiency, histocompatibility, or transient immunocompromise from large volume transfusion or bypass. Outside of these rare settings, acute GVHD is typically only seen in the context of allogeneic BMT (bone marrow transplantation).
The risk of acute GVHD is related to many clinical factors including:
Continue Reading
HLA (human leukocyte antigen) matching
The better matched the donor is to the recipient, the less the risk.
Donor type
Unrelated adult donors confer the greatest risk of acute GVHD; sibling donors have less risk.
Stem-cell source
Several studies have shown that peripheral blood stem cells carry greater risk for acute GVHD than bone marrow, but this finding is still controversial.
Children are at lower risk of developing acute GVHD than adults.
Donor age
Older donor age has been associated with increased risk of acute GVHD.
Donor gender
Female donors increase the risk of acute GVHD in male recipients.
Transplant conditioning intensity
Reduced or non-myeloablative transplants reduce the incidence, and delay the onset of acute GVHD.
Unrelated cord-blood transplants result in less acute GVHD for the same degree of HLA-mismatch
At this time, most cord-blood units are only partially matched to the recipient.
acute GVHD prophylaxis regimen
Ex vivo T-cell depletion or administration of anti-T-cell antibody therapies around the time of donor graft infusion (such as antithymocyte globulin or alemtuzumab) decreases the risk of acute GVHD.
Acute GVHD is staged on a scale of 0 to IV based on a composite score derived from each of the three target organs (skin, liver, GI [gastrointestinal] tract). (Figure 1)
What features of the presentation will guide me toward possible causes and next treatment steps:
Although acute GVHD can develop at any time following allogeneic BMT, the clinical symptoms typically develop between 3 to 4 weeks after the transplant in one of the classic target organs – the skin, liver or GI tract.
Clinical features include:
Maculopapular rash, commonly pruritic, often involving the palms and soles at first, but can spread to the entire body surface and, in severe cases, blister or ulcerate. Early stages can be difficult to distinguish from drug rash.
Features of cholestasis predominate with either elevated bilirubin levels in the blood or clinical jaundice. Elevated transaminase levels can occur around the initiation of liver GVHD, but are not a predominant feature.
GI tract
Usually presents as diarrhea from either the small intestine or colonic involvement. Nausea, vomiting, and anorexia are common manifestations of upper GI GVHD. Abdominal cramping, ileus, and bloody diarrhea are often seen in cases of more severe GI GVHD.
GVHD staging guides treatment steps. The overall GVHD grade is a composite score of the target organ stages (skin, liver, GI tract). (Figure 1)
What laboratory studies should you order to help make the diagnosis and how should you interpret the results?
Acute GVHD is a clinical diagnosis. Laboratory studies are not required (other than an elevated bilirubin which is necessary to diagnose liver GVHD). However, biopsies of affected organs (skin, upper GI tract, lower GI tract, liver) can be useful in confirming the clinical impression.
Pathological findings, such as vacuolar interface dermatitis with apoptotic keratinocytes for skin GVHD and epithelial cell apoptosis in the intestinal mucosa for GI GVHD, are often seen.
Infectious etiologies for diarrhea should be ruled out, such as Clostridium difficile, rotavirus, and adenovirus infections.
A drug rash can usually be distinguished from skin GVHD on biopsy.
Endoscopic evaluation can help identify other causes of GI symptoms such as nausea, vomiting, and diarrhea such as gastritis or Cytomegalovirus (CMV) colitis.
What conditions can underlie acute graft-versus-host disease:
Acute GVHD is a clinical diagnosis that is typically only suspected in the appropriate clinical scenario, primarily allogeneic BMT, but rare cases of transfusion-associated or maternal transfer of lymphocytes into an immunocompromised neonate can result in acute GVHD.
When do you need to get more aggressive tests:
Because acute GVHD is the primary cause of non-relapse mortality in allogeneic BMT, it is important to aggressively test for acute GVHD relatively early after the diagnosis is suspected. Tissue biopsies obtained very early in the disease course are sometimes non-diagnostic, but that should not preclude re-biopsy and/or treatment if the diagnosis is strongly suspected.
What imaging studies (if any) will be helpful?
Imaging studies are generally not helpful in the diagnosis of acute GVHD. Confirmation of ileus by abdominal CT (computed tomography) scan can be helpful during management.
What therapies should you initiate immediately and under what circumstances – even if root cause is unidentified?
Prevention is the most important strategy to limit acute GVHD. The primary aim of prevention is to deplete T-cells or prevent their proliferation in response to host antigens. There are numerous methods to achieve this goal, and institutional preference plays a large part in the selection of a GVHD prevention therapy.
Briefly, T-cell depletion, either in vitro or in vivo, can be effective in preventing severe GVHD, but are associated with increased risk of relapse, infection, and delayed immune reconstitution. The combination of a calcineurin inhibitor (tacrolimus or cyclosporine) with either mycophenolate or methotrexate is the most common GVHD prevention therapy. The risk of GVHD grade II or higher with this approach is 30 to 80% (based on the risk factors listed above) with the degree of the HLA match and donor type being the most important. HLA matched sibling donor transplant recipients have a 25 to 45% incidence of acute GVHD, compared to a 60 to 80% incidence in HLA mismatched unrelated donor transplant recipients.
Corticosteroid therapy
Acute GVHD grade I (limited skin rash less than 50% BSA [body surface area]) can often be treated with topical corticosteroid therapy alone. Approximately 50% of patients who present with GVHD grade I will progress to higher grade GVHD and require more intensive treatment. There is no reliable way to predict who will develop progressive GVHD, therefore, some clinicians choose to initiate systemic corticosteroid therapy in patients at high risk for developing a more severe GVHD, such as recipients of unrelated donor transplants or when GVHD has developed within 2 weeks of transplant. There is no convincing data to advise for or against this approach.
The standard therapy for acute GVHD grade II or higher is prompt initiation of high-dose corticosteroid therapy (prednisone 2mg/kg/d or equivalent methylprednisolone dose). Topical steroids for skin GVHD and non-absorbable steroids, such as oral beclomethasone for GI tract GVHD are useful adjunctive therapy.
Complete gut rest for lower GI tract GVHD is usually initiated promptly to minimize the risk of developing ileus or painful abdominal cramping. Reintroduction of a diet as the disease responds to therapy is a stepwise, slow process, starting with small volumes of clear liquids and advancing with the easiest to digest foods first.
What other therapies are helpful for reducing complications?
Corticosteroid related complications are among the most serious consequences of acute GVHD.
Prompt initiation of broad anti-infective coverage for bacterial, pneumocystis, viral, and fungal infections, especially with Aspergillus coverage, can be life-saving. Monitoring for and preemptive treatment of Cytomegalovirus (CMV) activation in at risk patients is also essential. All patients are at risk for CMV reactivation unless both donor and recipient where known to have negative CMV serology prior to transplant.
Other complications such as hypertension, diabetes, osteoporosis, and myopathy require constant monitoring and management. Renal impairment in patients treated with calcineurin inhibitors can be avoided or minimized by ensuring adequate hydration.
What should you tell the patient and the family about prognosis?
Approximately 50 to 65% of patients with acute GVHD respond to corticosteroid therapy within 4 weeks. Failure to respond to treatment within 4 weeks (that is, an improvement in GVHD grade by at least one grade) is associated with a poor prognosis; the 6 month mortality rate in these patients is 45 to 65%.
Patients who develop grade IV GVHD have a particularly poor prognosis with mortality rates approaching 90%.
Patients with steroid responsive GVHD have a better prognosis, but the 2 year non-relapse mortality is still 20 to 35%, with deaths most commonly due to infections or chronic GVHD. The development of acute GVHD is a major risk factor for chronic GVHD, which can become a debilitating illness in around one-third of cases.
"What if" scenarios.
Inadequate response to initial treatment
An inadequate response to initial treatment with corticosteroids should lead to the initiation of second line therapy. Standard indications for starting second line therapy include worsening of the GVHD grade after 3 to 5 days of systemic treatment or lack of response within 7 to 14 days.
Unfortunately, there is no standard approach for this scenario and large numbers of patients fail to respond. Second line agents that have shown some efficacy include antibody therapy (antithymocyte globulin, alemtuzumab), mycophenolate, TNF (tumor necrosis inhibitors (etanercept, infliximab), extracorporeal photopheresis, and pentostatin.
Flares during steroid tapers
Flares of GVHD during steroid tapers are another common scenario. These patients are considered to have steroid-dependent GVHD. Reversal of the steroid taper is almost universally performed, but the addition of steroid-sparing immunosuppressants, should be considered.
Management of life-threatening infections
One of the most challenging scenarios is management of life-threatening infections such as invasive fungal infections or end-organ viral diseases, such as CMV pneumonitis in patients with steroid-dependent GVHD. In this situation, the addition of steroid-sparing therapies, such as extracorporeal photopheresis may facilitate a successful steroid taper.
Skin breakdown
Excellent skin care is an important component of management. Blistering in severe skin GVHD can be managed like burns or other similar wounds. All patients, even those without skin GVHD, should be advised to avoid/minimize ultraviolet light exposure with clothing and sunscreen.
Severe diarrhea
The judicious use of antimotility agents can be helpful in controlling GVHD-related diarrhea. Octreotide infusions can occasionally be helpful as an adjunctive therapy for poorly responding, profuse diarrhea. Patients with GI tract diarrhea may be kept on gut rest for prolonged periods; therefore, early initiation of parenteral nutrition is important.
Debilitation and myopathy
Debilitation and myopathy from prolonged high-dose steroid therapy should be avoided/minimized with physical therapy.
Risk of osteoporosis
Osteoporosis prophylaxis is important in order to avoid later onset of fractures, such as vertebral compression fractures which can be very painful. Avascular necrosis is another common complication.
Acute GVHD is the consequence of donor T-cells responding to host antigens. Damage to the recipient tissues by the transplant conditioning regimen increases the likelihood of GVHD. The release of pro-inflammatory cytokines increases the expression of receptors on antigen-presenting cells (APCs), enhancing cross presentation of minor histocompatibility antigens to donor T-cells. Donor T-cells proliferate and secrete additional inflammatory cytokines, such as TNF. Target organ damage is the consequence of both cellular effectors and soluble factors like TNF.
What other clinical manifestations may help me to diagnose acute graft-versus-host disease?
At each encounter, a careful history for target organ symptoms should be obtained.
Pruritus sometimes precedes development of skin GVHD rash. Nausea, anorexia, and weight loss can signal the presence of upper GI-tract GVHD, but are often overlooked initially. Abdominal cramping, loose stools, watery or bloody diarrhea should prompt further work-up.
A thorough skin exam is an important aspect of every encounter in the at risk patient. A maculopapular rash is stereotypical, but sometimes erythema is the presenting finding. Rash involving the palms or soles in the at-risk patient is usually GVHD.
What other additional laboratory studies may be ordered?
Total bilirubin levels are mandatory as part of the acute GVHD staging. Eosinophilia on a complete blood count differential, while non-diagnostic, can be a clue to GVHD presence or impending onset.
What's the evidence?
Flowers, ME, Inamoto, Y, Carpenter, PA. "Comparative analysis of risk factors for acute graft-versus-host disease and for chronic graft-versus-host disease according to National Institutes of Health consensus criteria". . vol. 117. 2011. pp. 3214-9. [Multiple studies in the 1990's evaluated risk factors for acute GVHD. This recently published large study from a single center confirmed and extended prior observations. Of note, recipient age was not a statistically significant risk in this study.]
Rühl, H, Bein, G, Sachs, UJ. "Transfusion-associated graft-versus-host disease". . vol. 23. 2009. pp. 62-71. [Excellent review of settings in which GVHD can develop, other than allogeneic bone marrow transplantation.]
Ferrara, JL, Levine, JE, Reddy, P, Holler, E. "Graft-versus-host disease". . vol. 373. 2009. pp. 1550-61. [Comprehensive state of the art review of GVHD pathophysiology, prevention, treatment, and supportive care recommendations.]
MacMillan, ML, Weisdorf, DJ, Wagner, JE. "Response of 443 patients to steroids as primary therapy for acute graft-versus-host disease: comparison of grading systems". . vol. 8. 2002. pp. 387-94. [Highly cited paper describing expected treatment outcomes for patients treated for acute GVHD at a single center.]
Levine, JE, Logan, B, Wu, J. "Graft-versus-host disease treatment: predictors of survival". . vol. 16. 2010. pp. 1693-9. [Recent analysis of factors predictive for response and survival from a multicenter study of novel GVHD treatments.]
Pidala, J, Anasetti, C. "Glucocorticoid-refractory acute graft-versus-host disease". . vol. 16. 2010. pp. 1504-18. [Comprehensive review of treatment options for steroid refractory GVHD.]
Couriel, D, Carpenter, PA, Cutler, C. "Ancillary therapy and supportive care of chronic graft-versus-host disease: National Institutes of Health consensus development project on criteria for clinical trials in chronic graft-versus-host disease: V. Ancillary Therapy and Supportive Care Working Group Report". . vol. 12. 2006. pp. 375-96. [A workshop organized by the NIH (National Institutes of Health) developed recommendations for ancillary therapy and supportive care for chronic GVHD. These recommendations are highly applicable for patients requiring prolonged therapy for acute GVHD.]
Glucksberg, H, Storb, R, Fefer, A. "Clinical manifestations of graft-versus host disease in human recipients of marrow from HL-A-matched sibling donors". . vol. 18. 1974. pp. 295-304. [The data used in the figure within this chapter is based on the data in this article.]
Copyright © 2017, 2013 Decision Support in Medicine, LLC. All rights reserved.
No sponsor or advertiser has participated in, approved or paid for the content provided by Decision Support in Medicine LLC. The Licensed Content is the property of and copyrighted by DSM.
- Acute graft-versus-host disease
- What every physician needs to know about acute graft-versus-host disease:
- What features of the presentation will guide me toward possible causes and next treatment steps:
- What laboratory studies should you order to help make the diagnosis and how should you interpret the results?
- What conditions can underlie acute graft-versus-host disease:
- When do you need to get more aggressive tests:
- What imaging studies (if any) will be helpful?
- What therapies should you initiate immediately and under what circumstances – even if root cause is unidentified?
- What other therapies are helpful for reducing complications?
- What should you tell the patient and the family about prognosis?
- "What if" scenarios.
- Pathophysiology
- What other clinical manifestations may help me to diagnose acute graft-versus-host disease?
- What other additional laboratory studies may be ordered?
- What's the evidence?


text:
Robo Creative PSD Template
- -Easy to edit
- -Creative/digital agency PSD template.
- -Fresh and unique look
- -Layered PSD files / well organized
- -6 PSD Files
- -Multipurpose Template.
Credits Files Fonts and others
I've used the following fonts and assets as follow:
Special thanks to:
- Roboto Slab – Font used.
- Some Photos Used
- Other Photos Used
Note: Images are for preview purposes only, and are NOT included in the main PSD files.


text:
Wednesday, September 30, 2009
Butternut Squash Soup Tomorrow!
2 T olive oil
2 large onions
2 butternut squash
2 apples
1 T thyme (or seasoning of your choice)
salt and pepper, to taste
about 2-4 cups water (or chicken stock)
heavy cream or half and half
optional: honey, spinach, bacon, sour cream, lemon
A Preview...
Call or stop by The Willows to order your own special hats! Our own Willowette, Krista, specializes in themed party hats including birthdays, baby showers, even cooking parties! Use your imagination!
Tuesday, September 29, 2009
Saturday, September 26, 2009
Blabla clothes!
Wednesday, September 23, 2009
Put the books on the shelf first, then work in your display pieces - Brooke's tips are to keep the color palatte simple, add some sparkle, and relax! These items can always be changed up and moved around - in fact, that's what makes it fun!
Tuesday, September 22, 2009
First Day of Fall
Friday, September 18, 2009
Holiday Helper
Also did you know that The Willows has burlap pumpkins this year? Exclusive to The Willows! Quantities limited!
Wednesday, September 16, 2009
What Will Matter
By Michael Josephson
Ready or not, some day it will all come to an end.
There will be no more sunrises, no days, no hours, or minutes.
All the things you collected, whether treasured or forgotten will pass to someone else.
Your wealth, fame and temporal power will shrivel to irrelevant.
It will not matter what you owned or what you were owed.
Your grudges, resentments, frustrations, and jealousies will finally disappear.
So, too, your hopes, ambitions, plans, and to-do lists will all expire.
The wins and losses that once seemed so important will fade away.
It won't matter where you come from, or on what side of the tracks you lived.
It won't matter whether you are beautiful or brilliant.
Your gender, skin color, ethnicity will be irrelevant.
So, what will matter?
How will the value of your days be measured?
What will matter is not what you bought, but what you built;
What will matter is not your success, but your significance.
What will matter is not what you learned, but what you taught.
What will matter is every act of integrity, compassion, courage and sacrifice that enriched, empowered or encouraged others to emulate your example.
What will matter is not your competence, but your character.
What will matter is not how many people knew you, but how many will feel a lasting loss when you're gone.
What will matter is not your memories, but the memories of those who loved you.
What will matter is how long you will be remembered, by whom and for what.
Living a life that matters doesn't happen by accident.
Tuesday, September 15, 2009
Are You Listening?
Friday, September 11, 2009
Ready for Halloween!
But really, can anyone resist the Halloween decorations we have at The Willows???
Thursday, September 10, 2009
Tuesday, September 8, 2009
Wednesday Madness
Fall and Holiday patterns and colors available for order!
Most items in stock and ship immediately!
Also available to order from Vietri - garden, lamps, bath accessories, urns, glassware and flatware!
Fall Food for Thought
1 Vermont Mystic Pie Shell (any pie shell may be substituted)
12 oz Vermont Plain Yogurt
Saturday, September 5, 2009
Closed for Labor Day
See you Tuesday at our normal hours! Don't forget to come see vanilla chair - our new kid's boutique! Our games and girl's accessories are selling like hotcakes!
Friday, September 4, 2009
Toy Drive for Kids!
PLEA is also taking tax-deductible donations in the form of checks which can be dropped off at The Willows and made out to PLEA Charities.
We recommend you stop by and pick up one of the fun, eco-friendly and educational children's toys at vanilla chair - the new children's boutique inside The Willows!
Thursday, September 3, 2009
Hubband Swim Event!
The Most Amazing Cake in The World
*Note: To make - you must bake lots of layers separately and have lots of food coloring on hand!
Check out the rest of the back-to-school fun on Emily's blog!
Wednesday, September 2, 2009
Wednesday Madness
Tuesday, September 1, 2009
It's Fall at The Willows
Bev and Krista work on hanging an oversized oak leaf garland on a mirror.
Laurie makes a perfect fall table setting.


text:
housewife of the yearLIO - COMIX DISCOMIX
love love love this
the band Clorox Girls do a decent cover of "Banana Split."
and check out teki latex feat lio ! very nice new song Les matins de paris
By francelagale, at 23 December, 2006 03:40
Portuguesa Bonita
Good Job!" :)
Armageddon Thru To You
If you've been wondering why it seems like the world around us is unraveling, it's because the last days as foretold in the bible are now upon us. Just as it was 2000 years ago, many were unable to discern the signs of Jesus Christ's first coming (Mat 16:3), as will many concerning his second coming, which will occur very soon. Yes many have proclaimed a similar sentiment many times in the past, but their errors have no bearing on today other than to lull you into spiritual apathy, and that too was prophesied to occur in the last days.
If you're not a believer in Jesus Christ because you're an atheist, consider that the underlying impetus for your disbelief is most likely borne of pride and here's why:
When we die, if you as an atheist were right, then there is no upside or downside for anyone regarding the afterlife. We will all simply cease to exist
However if we Christians were right about our belief in the afterlife, then we will be given eternal life and you as an atheist will receive eternal damnation
Given the choices, the position held by an atheist is a fools bet any way you look at it because the atheist has everything to lose and nothing to gain. It is tantamount to accepting a "heads I win, tails you lose" coin toss proposition from someone. And that someone by the way is Satan (see Ephesians 6:12).
The only way to explain the attitude held by an atheist is pride, pure and simple. The intellectually dishonest and/or tortured reasoning used by atheists to try and disprove the existence of God is nothing more than attempts to posture themselves as superior (a symptom of pride). And as anyone who has read their bible knows, this is precisely the character flaw that befell Lucifer, God's formerly most high angel. (Isaiah 14:12-15). Is it any wonder then why the bible is so replete with references to pride as the cause of mankind's downfall?
Pride permeates our lives and burdens us in ways that most of us seldom recognize. Ironically, pride is the one thing that can blind someone to things even the unsighted can see. And sadly pride will blind many with an otherwise good heart, to accepting the offer of eternal salvation that Christ bought and paid for with his life.
In any event, if you're an atheist, I wish you only the best for every day of the rest of your life because for you, this life is as close to heaven as you'll ever get, but for believers in Christ, this life is as close to hell as we'll ever get.
If you're not a believer and follower of Jesus Christ because you are of another faith, please take the time to very carefully compare your faith to Christianity and ask yourself, why is the bible the only religious book with both hundreds of proven prophecies already fulfilled as well as those being fulfilled today? No other religion can claim anything remotely close to this fact. Many Christians who are serious students of bible prophecy are already aware of the role and significance of bible prophecy in foretelling end time events. God gave us prophecy as evidence of his divine holiness to know the begining from the end (Isa 46:10). God also believed prophecy to be so important that to those willing to read the most prophetic book in the bible, the Book of Revelation, he promised a special blessing (see Rev 1:3), and this is the only book in the bible that God gives its reader a special blessing for reading. Something to think about.
Don't risk losing Christ's offer of eternal life by not accepting him as your savior and by thinking that the bible is nothing more than a compilation of unrelated and scattered stories about people who lived 2,000 plus years ago. If you take the time to study (not just read) the bible, you will literally be shocked to learn things you would have never imagined would be revealed in it. Did you know that like parables, God also uses particular months and days in the Jewish calendar, Jewish Feasts and customs, solar and lunar phases, celestial alignments, gematria (Hebrew numerology) early bible events and more as patterns and models to foretell future events?
Consider the following interesting facts about the bible that testify to its God-inspired authorship:
Did you know that in Gen 12:2, God said he would bless Israel?. How else can you explain the grossly disproportionate level of success achieved by Jewish people as a tiny minority in the world, especially after all they have gone through? And how can you explain the success achieved by the tiny nation of Israel, surrounded by enemies outnumbering them 100 to 1 and yet still they remain victorious in all their wars?
Did you know that as evidence to indicate that Israel is the epicenter of the world from God's point of view is the fact that languages to the west of Israel are written and read from left to right as if pointing to Israel, and languages from countries to the east of Israel are written and read from right to left, again as though pointing to Israel. Just a coincidence, you say? I think not.
Did you know that the six days of creation and seventh day of rest in Genesis is a model for the six thousand years of this age (ending very soon), that is to be followed by a 1,000 year millennial reign by Christ (see 2 Peter 3:8)? Adam was born sometime prior to 4000 B.C., therefore our 6000 years are almost up.
Did you kow that the Gospel of Jesus Christ is hidden in the meaning of the Hebrew names listed in the genealogy of the book of Genesis (Research it online)? To deny this was God-inspired, one has to instead believe that a group of Jewish rabbis conspired to hide the Christian Gospel right inside a genealogy of their venerated Torah, which is not a very plausible explanation.
Did you know that solar eclipses, which the bible describes as the sun being black as sackcloth, and lunar eclipses, which the bible refers to as blood red moons, have prophetic meaning? Research it online. God showed Adam (and us) his plan for man's redemption through the use of celestial alignments. (research Mazzaroth online)
Did you know that much of the symbolism in the book of revelation refers to planetary alignments that will occur when certain events occur as prophesied? These planetary alignments also explained the birth of Christ, just search out The Bethlehem Star movie on the Internet.
Did you know that the references in Eze 39:4-17 and Rev 19:17-21 in the battle of Gog/Magog and Armageddon respectively, in which birds of prey will eat the flesh of the dead in battle from two enormous wars is based on fact? The largest bird migration in the world consisting of bilions of birds (34 species of raptors and various carrion birds) from several continents converge and fly over Israel every spring and fall. Coincidence? I think not.
Did you know that Hebrew numerology, also known as Gematria, and the numbers with biblical and prophetic significance are hidden in the Star of David? Google the video called "Seal of Jesus Christ"
Did you know that the seven Churches mentioned at the beginning of the Book of Revelation describe the seven stages the Church will go through?
There are literally hundreds of hidden messages in the bible like these that testify to the fact that the bible was God inspired, and statistically speaking, are all exponentially beyond the likelihood of any coincidence. You can find them yourselves if you only take the time to look into it. Remember Proverbs 25:2 "It is the glory of God to conceal a matter; to search out a matter is the glory of kings".
And finally, if you are Catholic, or one who subscribes to the emergent Church or seeker-friendly Church movement, please compare the doctrine taught, advocated or accepted by your Church, with the actual bible, notwithstanding some new-age version of the bible. And remember that although the bible is often referred to as the living bible, the word "living" was never intended to imply in any way that the bible "evolves" over time to meet, or be consistent with, the standards of man. It's just the opposite.
Well, am I getting through to you? If not, the answer might be explained in the response given by Jesus Christ in his Olivet discourse when he was asked by his disciples why he spoke the way he did (in parables, etc.) in the book of Matthew 13:10-16. What Jesus said could have easily been paraphrased more clearly as "so that the damned won't get it". Why did Christ respond the way he did when asked why he spoke this way? Is there something about pride (the bible says there is) that closes one's heart to seeing or hearing the messages supernaturally hidden in bible parables, models, typologies, and similes, etc.? That should give you something to think about, but don't take too long. Time is now very short.
If it sometimes seems like there are powers at work behind the powers we know in this world, or sinful/evil influences in your life, remember what it says in Ephesians 6:12 "For our struggle is not against flesh and blood, but against the rulers, against the authorities, against the powers of this dark world and against the spiritual forces of evil in the heavenly realms." If you study the bible, it will become clearer.
Did you know that God said to those unwilling to love the words of his truth and be saved, he would send them a strong delusion so that they would believe a lie. See 2 Thesalonians 2:10-11. Have you considered what this strong delusion might be? (i.e., evolution, climate change, or ?)
Have you considered the following. With so many self-professed Christians in the world, how is it possible that the bible can state that so few would find the path to eternal life (See Mat 7:14)? The answer: many Christians who practice Christianity practice an apostate version of it, and will ultimately not be county worthy (Luke 21:36) to escape God's wrath.
And by the way, if you are a scoffer, this too was prophesied to occur in the last days. See 2 Peter 3:3.
Thank you and God Bless you!
Armageddon.thru.to.you (at) gmail.com


text:
Free games
Adventure game where you play a child that can turn into a bird to explore a vast expanse and solve puzzles with an aesthetic like Journey meets Limbo and a great soundtrack
Epic Games
Torchlight II
Action RPG dungeon crawler similar to the Diablo series that has you playing as one of four classes as you explore randomly generated dungeons and hunt down the Alchemist
High profile Twitter accounts were hacked this Wednesday as part of a bitcoin scam, including the likes of Barack Obama, Joe Biden, Elon Musk, and Apple
No one's quite sure of how all the accounts were compromised, or to what extent Twitter's internal systems may have been affected, but Twitter was forced to temporarily block all verified accounts after their employee tools were used to hack even accounts using two-factor authentication
Anonymous sources claim that a Twitter employee was paid to either give access to other parties or post the tweets themselves, and a Twitter spokesperson says that the investigation is ongoing
Either way, this is a good example of why these kinds of tools and backdoor access can wreak havoc in the wrong hands. This may be one of the better arguments for end-to-end encryption
It all started when Elon Musk's account was compromised by a hacker using it to run a bitcoin scam, saying that any bitcoins payed to a specific address would be paid back two-fold (pay $1000, get $2000, was the example in the tweet)
Bill Gates' account was also hit, posting new tweets almost as fast as the old ones were deleted
Shortly after that the accounts of Apple, Uber, Obama, Jeff Bezos, Joe Biden, Kanye West, Mike Bloomberg, and many others including major online Bitcoin exchanges started all promoting the same scam
The bitcoin wallet linked to the tweets has had its balance fluctuating up and down as it does seem to be sending money somewhere, but it seems to have received nearly $120,000 USD worth of the cryptocurrency with more flowing through even up to Thursday evening when we're recording
Ubisoft Forward
Apparently the initial plan was to track how many minutes of the presentation each user watched and then reward them accordingly
Watch Dogs 2 for 1 minute of viewing, and so on for in-game rewards for The Division 2, Watch Dogs: Legion, and Assassin's Creed Valhalla
After some issues with their login portal, Ubisoft changed things up so that you just had to register your Ubisoft account at a particular URL (we tweeted it earlier this week) and you would eventually get all the rewards
A lot of users have been grumbling that they haven't received their rewards but their initial line of "it may take up to 24 hours" has slowly shifted to "Rewards will be delivered by the end of the week"
I just received mine a few hours before recording, so if you managed to register in time you should check your inbox
Ghost Recon Breakpoint is getting AI teammates this week, with full customization, sync shots, and the ability to revive the player, along with some improvements to Ghost War and a new live event called Resistance
Resistance offers limited-time missions that will affect the presence of rebels in Auroa, as well as offer exclusive rewards for participating
Watch Dogs: Legion looks pretty cool, giving you the ability to build you own crew of up to 40 operatives, but as noted by Fanily member Asa its October 29th release date is butting right up against Assassin's Creed Valhalla and Cyberpunk 2077
Valhalla is coming November 17th, letting players lead Viking raids, assault castles, assassinate targets, build alliances and make their mark on England's Dark Ages
Most importantly you can recruit a cat to join your raiding party and keep the ship free of rats
Rainbow Six Siege is celebrating its 5 year anniversary with a message of thanks for the community's dedication
Hyper Scape is now in open beta, bringing the sci-fi multiplayer shooter to PC players for free
Far Cry 6 will hit on February 18th and have you fighting to free your homeland of Yara from a brutal tyrant played by Giancarlo Esposito (Gus Fring in Breaking Bad, Moff Gideon in The Mandalorian), and I'm tempted to buy the game just because of him
Ubisoft's going all-in on mobile
They showcased last year's Might & Magic Era of Chaos
Brawlhalla is coming to Android and iOS on August 6th with cross-play and special rewards for early-adopters
Tom Clancy's Elite Squad is a F2P tactical RPG hitting Android and iOS on August 27th with a roster of characters spanning the Tom Clancy universe
Apple Updates
iOS 13.6
Introduces more options for controlling automatic updates, so instead of either having it download and install automatically or you do everything manually, now you have have your device download future updates and then prompt you that it's ready
Updates will only be downloaded on Wifi
They've also brought in support for CarKey, which can let you use your iPhone or Apple Watch instead of your key fob for NFC-enabled cars
Not a lot of people will be able to take advantage of this, since it's pretty much limited to BMW at the moment, and requires at minimum an iPhone XR or Apple Watch 5, but once it's more widely available you'll see people unlocking their cars by tapping their phone on the handle, and starting them by putting their phone on the car's charging tray
You'll also be able to set up limitations on young drivers and share or revoke keys with up to five other users
Health now has a new Symptoms section that you can use to track things like aches, appetite changes, coughing, nausea, and more
Apple News can now save your place in long articles, letting you get back into things where you left off, and also has a new audio feature for News+ that has professionally narrated content
There are also a bunch of bug fixes, like one that had some phonecalls from Saskatchewan appearing as if they were from the US
watchOS 6.2.8 gives us support for those CarKey features, as well as ECG support in Bahrain, Brazil, and South Africa
Apple has posted a support document this week warning customers against using camera covers on their MacBooks, saying that it can lead to display damage due to the small amount of space allowed between the screen and body
Even if you don't see physical damage, it can also affect the light sensors used for screen brightness and the TrueTone display
They say anyone concerned about their camera should keep an eye out for the green light beside the lens, which is engineered so that the camera can't be access without it turning on
They also say that, if you really need a cover, they recommend one no thicker than a piece of printer paper that won't leave adhesive residue
This week in past game news:
July 11 – 1993 – Goof Troop on SNES
Goof Troop is an action-adventure video game, developed and released by Capcom in 1993 for the Super Nintendo Entertainment System, and based on the television series of the same name. The game can be played in multiplayer mode, wherein one player controls Goofy and the other Max.
Goof Troop is one of the first games designed by Shinji Mikami.
Shinji Mikami is a Japanese video game designer, director, and producer. Starting his career at Capcom in 1990, he went on to direct many of the company's biggest titles. He directed the first installment of the survival horror series Resident Evil in 1996 and the first installment of Dino Crisis in 1999. He returned to Resident Evil to direct the critically acclaimed remake of the first game in 2002. He returned to direct third person shooter Resident Evil 4 in 2005. In 2006, he directed his final Capcom game God Hand, a beat 'em up action game. Mikami worked at PlatinumGames to direct the third person shooter Vanquish in 2010. After that he created his own studio Tango Gameworks. Under that company, he directed the third person horror game The Evil Within. The company has since been acquired by the American company ZeniMax Media.
July 12 – 1985 – Acclaim acquires Sculptured Software, renames it Acclaim Studios Salt Lake City
This studio is responsible for the Super Star Wars games, which are terrible representations of Star Wars and games made difficult to extend play time.
July 13 – 2010 – Fruit Ninja on iPad Releases
iPhone version released a few months prior, this mobile game dominated peoples attention when it blew up on iPad. And still is being remade and released, as recently as April 2019, for Oculus Quest.
July 14 – 1998 – Civilization Name Case settled
MicroProse, Avalon-Hill, and Activision have settled the Civilization name issue out of court. MicroProse is the undisputed owner of the franchise (both computer and board games). Activision gets a license for "Civilization: Call to Power" and one add-on. Avalon-Hill relinquishes all rights to MicroProse.
July 15 – 2003 – Star Wars: Knights of the Old Republic
The story of Knights of the Old Republic takes place almost 4,000 years before the formation of the Galactic Empire, where Darth Malak, a Dark Lord of the Sith, has unleashed a Sith armada against the Republic. The player character, as a Jedi, must venture to different planets in the galaxy to defeat Malak.
July 16 – 2005 – Dance Dance Immolation
Dance Dance Immolation was an interactive performance piece by fire art group Interpretive Arson based out of the artist work space known as NIMBY in East Oakland. It is a modified version of Dance Dance Revolution where players are shot with fire if they perform poorly. Participants are not harmed since they wear a fire proximity suit with forced-air respirators. Numerous other safeguards are built into the system to ensure the players are not subject to direct flame exposure or inhalation of superheated air. The piece was premiered in 2005 and ran at various festivals and private events internationally. It was retired in 2013 at Burning Man, where all the components were gathered into a pile and a piano was dropped on it.
July 17 – 2017 – Redneck Deer Huntin'
Redneck Deer Huntin' is a hunting game for the PC using the same engine as the previous games in the series. It was developed by Xatrix Entertainment and released in 1997.
The class action lawsuit against Apple's silent performance throttling has concluded, and eligible iPhone owners can get about $25 each if they submit a claim online
The class includes any US resident who owned any iPhone between 6 and 7 Plus before December 21, 2017. You must also have experienced "diminished performance" on your device
If you want your share, or you want to opt out so you can sue Apple individually (good luck), you can go to smartphoneperformancesettlement.com
Walmart is bringing their weight into the mask-wearing debate, requiring customers to cover their faces in all locations
Since governments have failed to set the tone and tell citizens to wear a mask whenever they need to leave the house, businesses like Walmart, Costco, and Apple have been cracking the whip to prevent COVID outbreaks
Walmart will apparently be bringing on specially trained "health ambassadors" stationed by store entrances to enforce the new rules
According to PCGamer, Halo 3 is the best PC port of the Master Chief Collection so far
Many were worried, especially after Reach's issues with sound and frame rate since it runs on a modified Halo 3 engine, but apparently Halo 3 runs perfectly with a full 144fps without the animation issues of some of the other MCC titles
Gizmodo hit the panic button this week, screaming about a major Windows security patch that everyone needs to install, if they're running Windows Servers, anyway
The bug is related to the Windows Domain Name System, and it is a pretty nasty one, so if you're running Windows Server you should absolutely update as soon as possible. Most people won't need to do anything, though
Ubisoft's chief creative officer, managing director of Canadian studios, and their global head of HR have all resigned effective immediately following a review centred around sexual misconduct charges
This follows the departure of their vice president, Maxime Béland, after similar allegations
Half-Life: Alyx is damn good.
Played on an Oculus Quest using Virtual Desktop
It takes a little finessing to get things running smoothly for wireless PC VR, but after a little guess-and-check (H.264 vs HEVC) I spent a couple hours in the game with no issues at all
The environments are great, locomotion is solid, gunplay and reloads are satisfying, there's no melee combat so far, but the grabbity gloves are fantastic
The gloves let you point your hand at an item out of range, press a button, and flick your wrist to have it launch itself toward you
Then it's really intuitive to catch it on its way past your head and either put it in your ammo inventory over your shoulder or your item inventory in your wrists
Overall this really feels like a triple-A VR game, and I very much hope we can get more like it
For more content, Patreon supports get access to upcoming ideas and more!
Thank you Breanne, our podcast friend and someone we don't want to miss out on! 😉