[ dropped d-x ] Hey all,
Thanks for this bug and the work so far. I just wanted to give a couple
of thoughts, and maybe later on help with the patch if that's useful.
> We can likely do with a single control file entry like:
>
> X-Vcs-Upstream-Git: <url> -b <branch>
>
> which would match the existing Vcs-* syntax.
What do you imagine the `-b' switch doing? For me I am mainly interested
in upstream's commits to use with `--upstream-vcs-tag'. Maybe it creates
a tracking branch 'upstream/<branchname>'?
My real main question, though, is about derivatives. I mainly work on
Ubuntu, and for GNOME stuff we're starting the process of converting off
our bzr branches to base on top of Debian's gbp repositories. In order
to pull new commits/uploads, we need to have Debian's commits available
to `git merge' with. There's a not-consistently-followed-but-could-be
convention of using
XS-Debian-Vcs-$VCS: $foo
in d/control when updating Vcs-Git to represent the (distro) upstream's
VCS. It'd be good to use this, or some other metadata, to set up a
`debian' remote too. Questions:
- Would this be acceptable?
- How do we know what to put in the middle of the field there? One
answer is the 'Parent' distribution:
laney@nightingale> dpkg-vendor --query Parent # running on Ubuntu
Debian
? Or we could just directly specify this in gbp.conf when forking a
repsitory from Debian:
[ clone ]
extra-remotes = debian,someurl xxx,yyy ...
Cheers,
--
Iain Lane [ i...@orangesquash.org.uk ]
Debian Developer [ la...@debian.org ]
Ubuntu Developer [ la...@ubuntu.com ]
signature.asc
Description: PGP signature
