Ian Jackson <ijackson@chiark.greenend.org.uk> writes:
> Ansgar 🙀 writes ("Re: [RFC] General Resolution to deploy tag2upload"):
>> On Thu, 2024-06-13 at 05:58 +0800, Sean Whitton wrote:
>> > tag2upload already supports most existing workflows (including the one
>> > you yourself prefer, where only debian/ is committed to git).
>>
>> How does this work? Does the builder run the `get-orig-source` target
>> in debian/rules?
>
> No. The git commitid of the upstream source is named in the tag
> generated by git-debpush. (So that upstream git branch has to be in
> your git repo somewhere - just not in your branch.) The t2u server
> will use that (ultimately, via git-archive).
How does t2u find out the URL to the upstream git repository? Is
https:// enforced, or are http:// or git:// URLs supported? Is the
upstream git branch recorded anywhere, or just the commit?
Where is this documented? I feel I should have understood this already,
but I have tried to read links posted so far...
/Simon
Attachment:
signature.asc
Description: PGP signature