Hi Daniel, Dne 12.10.2024 (sob) ob 16:50 +0200 je Daniel Gröber napisal(a): > > Looks good. I've uploaded it as 0.4.6-2. >
Thanks for the reply and upload. > Could you report an upstream issue about the problems we're working around > here? This is really just hiding real problems for now. > > There's also a request to update to the latest upstream version: > https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1081945 did you see it? > > You should really respond to bugs :) > Now, that our current changes are being uploaded i intend to update git-subrepo to current upstream version and i'll report an upstream issue with the updated set of our changes together with the description of their purpose. What kind of response to bugs did you mean, except for working on the bug and provide changes? Do i need to subscribe to the bug?... > > Dne 07.09.2024 (sob) ob 19:22 +0200 je Daniel Gröber napisal(a): > > > If > > i.e. debian/git-subrepo changes in a way that i can not fast forward from > > it, > > then i'll have to force-pull and consequently force push into may repo > > again. > > Do you agree? > > No. You'll want to rebase (cf. https://git-rebase.io/#pull) to put your > changes back on top of the remote changes. > Sure:) What i meant regarding force-push: If debian remote changes in a way that its last commits differ from last commits in my (salsa) remote, then i'll have to force push into my remote, also after using rebase (which i should) to incorporate debian remote into my local clone. --Samo
