Bug#888313: please allow git remote configuration (e.g. for upstream remote)

Hi Iain, (it seems this never ended up in my inbox, so sorry for the late reply): On Mon, May 14, 2018 at 11:11:33AM +0100, Iain Lane wrote: > [ 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

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

[ 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: -b > > which would match the existing

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

Hi, Thanks for having a look. On Tue, Feb 13, 2018 at 09:59:02AM +0100, Michael Stapelberg wrote: > See the attached work-in-progress patch for how far I got at this point. > Before I continue, here are two questions: > > AFAICT, the control package doesn’t allow me to do case-insensitive >

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

See the attached work-in-progress patch for how far I got at this point. Before I continue, here are two questions: AFAICT, the control package doesn’t allow me to do case-insensitive lookups. Should we extend it to do that, or do we really want to insist on users capitalizing the directives

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

When cloning a git repository containing Debian packaging (no matter whether you use git-clone or gbp-clone), you’ll end up with one or more branches all tracking the remote from which you cloned (e.g. alioth, or salsa). In debian-x, there is

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

On 02/11/2018 02:20 PM, Michael Stapelberg wrote: > Given that it has been two weeks, I don’t think we’re going to get a > reply from debian-x :) It's not clear to me what the question is. I've also never used git-buildpackage, so may be missing context. Cheers, Julien > > I’d suggest to just

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

On Sun, Feb 11, 2018 at 02:20:55PM +0100, Michael Stapelberg wrote: > Given that it has been two weeks, I don’t think we’re going to get a reply > from debian-x :) Agreed. > > I’d suggest to just go ahead — I can’t see why the suggested approach > wouldn’t work for debian-x, and even if they

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

Given that it has been two weeks, I don’t think we’re going to get a reply from debian-x :) I’d suggest to just go ahead — I can’t see why the suggested approach wouldn’t work for debian-x, and even if they need something on top, it’d be easy to add that later. Guido, how do we proceed? Do you

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

Hi, On Thu, Jan 25, 2018 at 09:32:01AM +0100, Michael Stapelberg wrote: >On Thu, Jan 25, 2018 at 8:11 AM, Guido Günther <[1]a...@sigxcpu.org> wrote: > > Hi Michael, > On Wed, Jan 24, 2018 at 10:27:25PM +0100, Michael Stapelberg wrote: > > Package: git-buildpackage > >

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

Sorry about that. Maybe it would be good to update the header of http://x.debian.net/reference/git-usage.html with up-to-date contact info, in that case :) On Thu, Jan 25, 2018 at 9:38 AM, Cyril Brulebois wrote: > Hi, > > Quoting in full for debian-x@: > > Michael Stapelberg

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

Hi, Quoting in full for debian-x@: Michael Stapelberg (2018-01-25): > On Thu, Jan 25, 2018 at 8:11 AM, Guido Günther wrote: > > > Hi Michael, > > On Wed, Jan 24, 2018 at 10:27:25PM +0100, Michael Stapelberg wrote: > > > Package: git-buildpackage > > >

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

On Thu, Jan 25, 2018 at 8:11 AM, Guido Günther wrote: > Hi Michael, > On Wed, Jan 24, 2018 at 10:27:25PM +0100, Michael Stapelberg wrote: > > Package: git-buildpackage > > Version: 0.9.6 > > Severity: wishlist > > > > When using a pure git workflow (no tarballs involved), as

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

Hi Michael, On Wed, Jan 24, 2018 at 10:27:25PM +0100, Michael Stapelberg wrote: > Package: git-buildpackage > Version: 0.9.6 > Severity: wishlist > > When using a pure git workflow (no tarballs involved), as documented in >

Bug#888313: please allow git remote configuration (e.g. for upstream remote)

Package: git-buildpackage Version: 0.9.6 Severity: wishlist When using a pure git workflow (no tarballs involved), as documented in file:///usr/share/doc/git-buildpackage/manual-html/gbp.import.upstream-git.html, it is common to configure the “upstream” git remote to be the actual upstream,