Re: backport python-astropy for jessie?
On Fri, Feb 03, 2017 at 01:18:40AM -0500, Leo P. Singer wrote:
> Git will not let me name the branch 'debian/jessie-backports' because there is already a branch called 'debian':
> $ git branch -m debian/jessie-backports
> error: 'refs/heads/debian' exists; cannot create 'refs/heads/debian/jessie-backports'
> fatal: Branch rename failed
> Apparently, it is a known issue with git that you cannot create a branch 'foo/bar' if branch 'foo' exists:
> Since it looks like most debian-astro packages have a 'debian' branch rather than 'master', is it OK if for debian-astro we instead adopt the practice that backports go in the 'jessie-backports' branch?
If the Debian Astro team is doing things consistently that's pretty fine
for me. For outsider / newcomers its helpful if its written down
somewhere when deriving from what other teams consider standard,