Package: git-flow
Version: 1.12.0-1
Severity: normal

Dear Maintainer,

    version 1.12 lost defaults:


## 1.12 behaviour

$ mkdir repo && ( cd repo && git init && git flow init -d )

Initialized empty Git repository in /tmp/repo/.git/
Using default branch names.
No branches exist yet. Base branches must be created now.
Branch name for production releases: [master] 
Branch name for "next release" development: [develop] 

How to name your supporting branch prefixes?
Feature branches? [] 
Bugfix branches? [] 
Release branches? [] 
Hotfix branches? [] 
Support branches? [] 
Version tag prefix? [] 
Hooks and filters directory? [/tmp/repo/.git/hooks] 


## 1.10 behaviour

$ mkdir repo && ( cd repo && git init && git flow init -d )

Initialized empty Git repository in /tmp/repo/.git/
Using default branch names.
No branches exist yet. Base branches must be created now.
Branch name for production releases: [master] 
Branch name for "next release" development: [develop] 

How to name your supporting branch prefixes?
Feature branches? [feature/] 
Bugfix branches? [bugfix/] 
Release branches? [release/] 
Hotfix branches? [hotfix/] 
Support branches? [support/] 
Version tag prefix? [] 
Hooks and filters directory? [/tmp/repo/.git/hooks] 



As upstream acknowledged this as a bug and fixed it[1], could
you please consider upgrading package to newest stable version?


Thank you, regards


[1] https://github.com/petervanderdoes/gitflow-avh/issues/393


-- System Information:
Debian Release: 10.0
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8), 
LANGUAGE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages git-flow depends on:
ii  git [git-core]  1:2.20.1-2

git-flow recommends no packages.

git-flow suggests no packages.

-- no debconf information

Reply via email to