On Sat, Aug 03, 2013 at 06:45:36PM +0900, Charles Plessy wrote: > Le Sat, May 12, 2012 at 07:38:36AM +0200, Andreas Tille a écrit : > > > > we have some record on our Debian Med mailing lists that I several times > > endet up with a clone that did not contained pristine-tar branch and I > > admit that I will forget this additional detail also in the future. I > > have no idea about internals but IMHO it would be a very good idea if > > git-buildpackage would work out of the box without specifying additional > > options. > > I would like to ask again if it would be acceptable to make --git-track='*' > the > default for debcheckout, since it does not consume more disk space or > bandwith.
Creating local branches for relevant remote branches is a normal part of working with git repositories, so I see no need to diverge from git's default behavior and creating local branches for all remote branches by default. debcheckout is intended to be a simple wrapper around $vcs to easily get the development source of a package, not much more. Note that "git checkout $branch" will automatically create a local branch based off the remote branch of the same name if it's unique, which should be the case with pristine-tar. Given that, there's not even a required change in workflow needed. Also, Andreas is talking about having git-buildpackage "work out of the box" in the initial report, so I'm not sure why this was filed against debcheckout. If this is about git-buildpackage's behavior, then the bug should be reassigned. If you feel strongly that debcheckout is the one that needs to be changed, then at most I could see adding a config variable to specify a user-specific value for --git-track. Cheers, -- James GPG Key: 4096R/331BA3DB 2011-12-05 James McCoy <james...@debian.org>
signature.asc
Description: Digital signature
