On Fri, 11 Sep 2020, Andreas Tille wrote:
> My guess is that the Salsa API provides means to script everything. Is
> there any existing script that supports this or is there any volunteer
> to write it. I would start migrating Debian Med, Debian Science and
> R packaging team repositories once gb
Le 11/09/2020 à 22:10, Richard Laager a écrit :
> On 9/11/20 11:26 AM, Xavier wrote:
>> $ salsa --group xx-team --all --no-fail rename_branch \
>> --source-branch=upstream --dest-branch=master
>
> Should "upstream" be "upstream/latest"?
Yes of course, you can choose source and dest
>
On 9/11/20 11:26 AM, Xavier wrote:
> $ salsa --group xx-team --all --no-fail rename_branch \
> --source-branch=upstream --dest-branch=master
Should "upstream" be "upstream/latest"?
As I understand it, "master" is correct if it is the upstream git
"master", but "upstream/latest" is cor
Bad list, repost here:
> Le 11/09/2020 à 18:14, Xavier a écrit :
>> Le 11/09/2020 à 12:42, Paolo Greppi a écrit :
>>> Hi Andreas,
>>>
>>> Il 11/09/20 12:16, Andreas Tille ha scritto:
Hi,
in teams where I have lots of packages (summing up to more than 1000)
I've touched) we foll
Le vendredi 11 septembre 2020, Paolo Greppi a
écrit :
> Hi Andreas,
>
> Il 11/09/20 12:16, Andreas Tille ha scritto:
>> Hi,
Hello,
>> in teams where I have lots of packages (summing up to more than 1000)
>> I've touched) we followed the gbp default and have branches
>>
>> master
>> upstr
Hi Andreas,
Il 11/09/20 12:16, Andreas Tille ha scritto:
> Hi,
>
> in teams where I have lots of packages (summing up to more than 1000)
> I've touched) we followed the gbp default and have branches
>
> master
> upstream
> pristine-tar
>
> and this is also the layout fixed in those
Hi,
in teams where I have lots of packages (summing up to more than 1000)
I've touched) we followed the gbp default and have branches
master
upstream
pristine-tar
and this is also the layout fixed in those team policies. I admit I
don't have strong feelings about branch names but I'
7 matches
Mail list logo
