2010/10/19 Yaroslav Halchenko <y...@debian.org>: > > On Tue, 19 Oct 2010, James Vega wrote: >> If it's the latter, then why not make >> the branch from which the Debian package is built the default branch of >> the repository? > > and that is the approach the other member of our NeuroDebian team > adheres to -- sets up custom push refs so whatever is present on alioth > as "upstream" branch gets pushed into github (where he collaborates with > upstream) as the "master" branch.
That's not what I'm referring to. If you run the git-symbolic-ref command I mentioned on Alioth, then a git clone of that repo will checkout the debian branch by default instead of the master branch. Since the Alioth repo is primarily for Debian development, this difference in the default branch makes sense, IMO. > Clearly that requires local setup in > .git/config and creates too much of "undocumented" customization > to my taste... imho having branch names corresponding among different > clones for the same repository is less confusing; and is plain situation > for the former case (upstream repo is also serving debian/ packaging in > a branch) The branch names of the remote repositories aren't being changed. Just which one is checked out as part of a clone. Granted, this doesn't work in the case where you're pointing to an upstream repository since in that case it makes more sense for the default branch to be related to upstream development. >> 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. > > even though I liked my little snippet -- I agree that use of such > heuristics is unreliable. > > Do you think it might be feasible to support > X-Vcs-debian-branch > or just > X-Vcs-branch > field which would instruct explicitly which branch to use? A Vcs-Branch field for the VCSes that support specifying which branch to get for a "clone" might be useful. -- 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