| Commit message (Collapse) | Author | Age |
|
|
|
|
| |
Most of it is GPL v2 or v3 licensed. Some parts only v2 atm, but I will
check with authors for v3 permission
|
|
|
|
| |
This fixes https://github.com/openSUSE/osc/issues/118
|
|
|
|
| |
Otherwise it's impossible to pass messages spanning over multiple lines.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This reverts commit b6ccac1ebd9cac5998118a7bb119508ade6b47fe.
This kind of functionality does not belong into vc. Source services
have far more knowledge about changes applied to packages and thus are
far more suitable to generate proper changelog entries. For example:
- tar_scm can generate changes entries from git logs
- refresh_patches can generate changes entries for added, removed
and rebased patches (it does that semi-automatically)
For both services, changelog generation is _opt-int_. That means it has
to be enabled explicitly via the 'changesgenerate' parameter.
Lastly, the format was broken anyway...
|
|
|
|
| |
This reverts commit 6f9f48e88eea2d14a6ce5ba928de0d8ad972cba3.
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
| |
Automatically add information about added, removed or modified patches, when
editor is invoked. That means when -m is passed or file with comment is
passed, no record is added.
Signed-off-by: Tomáš Čech <sleep_walker@suse.cz>
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
rather "vc") changes file mode of .changes file)
|
|
|
|
| |
osc vc
|
|
|