On 2014-08-22 11:08:17, Felipe Sateler wrote: > Resurrecting an old thread > > On Sat, Apr 6, 2013 at 4:32 AM, Reinhard Tartler <siret...@gmail.com> wrote: > > Hi, > > > > Recently, Russ' blog post was echoed on http://planet.debian.org: > > > > http://www.eyrie.org/~eagle/journal/2013-04/001.html > > > > In that post, he describes how to combine both the "import tarball" > > and the "have upstream history" available in the upstream packaging > > branch. AFAIUI, the heavy work is implemented in git-buildpackage's > > --upstream-vcs-tag <tag> option. > > > > While that option is news to me, I wonder if maybe anyone else already > > experiments with this? Does the team feel that making it mandatory for > > our package would be beneficial and appropriate? > > I know some in the team have experimented with this new workflow. > Could you share your experiences with it? I'm thinking that we should > encourage this workflow a bit more: it makes collaboration with > upstream easier (in both directions). However I'm still not too clear > on what would it look like, so I'd like to hear from people that have > been using it about their thoughts. > > Questions of interest: are you using gbp pq? If not, how do you pick > patches from upstream? How do you post patches back to upstream?
I'm not a great fan of the toolchain around packages in git. I like to store packages and git and also enjoy the default git-import-orig (with pristine-tar) layout, but that's about the only command I use from git-buildpackage besides tagging the Debian revision and exporting the orig tarball. All the other tools just couldn't convince me. Most of the time I write patches directly against the upstream repository and forward them from there. And if I take patches from the upstream repository, I export them from there, apply them to the package and do the quilt refresh dance if necessary. Cheers -- Sebastian Ramacher
signature.asc
Description: Digital signature
_______________________________________________ pkg-multimedia-maintainers mailing list pkg-multimedia-maintainers@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-multimedia-maintainers
