On Tue, Oct 19, 2010 at 1:32 PM, Yaroslav Halchenko <deb...@onerussian.com> wrote: > For quite a few packages of mine I use non-default branch to contain debian > packaging on top of the upstream sources. Such happens due to various reasons > (e.g. I am also involved in upstream development and master branch in GIT > tracks actual upstream development).
Do you mean that the git repository is being hosted with the upstream repository or just that the repository for the Debian package also contains the upstream sources? If it's the latter, then why not make the branch from which the Debian package is built the default branch of the repository? For example, running the following on the repository advertised in your Vcs-* fields will change which is the default branch that gets checked out (assuming your "debian" is the correct branch). git symbolic-ref HEAD refs/heads/debian I don't think adding heuristics to debcheckout about which branch should be considered the "default" branch is the right thing to do. The suggested heuristics aren't guaranteed to be correct (multiple branches may have a debian/changelog or debian/gbp.conf). Also, the suggested mechanism means that the branch that gets checked out will vary based on when the checkout is performed. -- James GPG Key: 1024D/61326D40 2003-09-02 James Vega <james...@debian.org> -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
