mirror of
https://github.com/xen-project/xen.git
synced 2026-10-28 10:11:27 +01:00
Ian Jackson
eff2fbe4dd
Preparing a real release, not just an RC, involves making commits. Typically, those will be on staging-$x. The tag will refer to them, and the checklist already says to push them to xenbits. But if the *branch* is not pushed, then people who just "git fetch" won't get the tag because it refers to commits they don't have. (Because of the strange rules git has about tag fetching.) Worse, the same may be true of people who "git clone". And anyway, those commits *should* be fed to staging-$x. Signed-off-by: Ian Jackson <Ian.Jackson@eu.citrix.com> Acked-by: George Dunlap <george.dunlap@citrix.com>
xen-bugtool =========== The xen-bugtool command line application will collate the Xen dmesg output, details of the hardware configuration of your machine, information about the build of Xen that you are using, plus, if you allow it, various logs. The information collated can either be posted to a Xen Bugzilla bug (this bug must already exist in the system, and you must be a registered user there), or it can be saved as a .tar.bz2 for sending or archiving. The collated logs may contain private information, and if you are at all worried about that, you should not use this tool, or you should explicitly exclude those logs from the archive. xen-bugtool is wholly interactive, so simply run it, and answer the questions.