or
or
By clicking below, you agree to our terms of service.
New to HackMD? Sign up
Syntax | Example | Reference | |
---|---|---|---|
# Header | Header | 基本排版 | |
- Unordered List |
|
||
1. Ordered List |
|
||
- [ ] Todo List |
|
||
> Blockquote | Blockquote |
||
**Bold font** | Bold font | ||
*Italics font* | Italics font | ||
~~Strikethrough~~ | |||
19^th^ | 19th | ||
H~2~O | H2O | ||
++Inserted text++ | Inserted text | ||
==Marked text== | Marked text | ||
[link text](https:// "title") | Link | ||
 | Image | ||
`Code` | Code |
在筆記中貼入程式碼 | |
```javascript var i = 0; ``` |
|
||
:smile: | ![]() |
Emoji list | |
{%youtube youtube_id %} | Externals | ||
$L^aT_eX$ | LaTeX | ||
:::info This is a alert area. ::: |
This is a alert area. |
On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?
Please give us some advice and help us improve HackMD.
Syncing
xxxxxxxxxx
Proposal: Using automatic release macros in RPM spec files
Notes:
Normal release flow
The most common case is release numbers which just get incremented for each build. For these, one could put the following into your spec file, to be filled in automatically:
Effectively resulting in:
Prereleases
As per the Fedora Versioning Guidelines, release fields for pre-release versions have to stay below 1. To accommodate this, another macro could be used with an option:
Example result:
Hotfixes
If you need to do a hotfix in an older Fedora version which doesn't affect newer ones, you would append a
<minorbump>
number to the release field so that upgradeability is ensured. This could also be done using an option:Example result: