Le 22/09/2014 21:04, Felix Natter a écrit :
> Shawn Sörbom writes:
>
>> Thats why I wanted to use gbp, I was afraid of missing details.
>
> It's really not that bad:
>
> 1. make sure your repo knows about its github "origin"
> 2. push each branch (if you used push -u once, then for subsequent
Shawn Sörbom writes:
> Thats why I wanted to use gbp, I was afraid of missing details.
It's really not that bad:
1. make sure your repo knows about its github "origin"
2. push each branch (if you used push -u once, then for subsequent
pushes you can mit the "origin master")
3. push all tags
Thats why I wanted to use gbp, I was afraid of missing details.
Ideally, I would have preferred to use Debian alioth servers, but after
reading the FAQ, I didn't think my package qualified.
Thank you both for your replies.
--Shawn
On Sunday, September 21, 2014 10:44:19 Felix Natter wrote:
> Dani
Daniel Lintott writes:
> So the workaround for this is to simply create an empty repo via the
> GitHub web interface and push to that. So if you already have you
> package prepared using Git:
>
> 1. git remote add origin g...@github.com:user/repo.git
> 2. git push -u origin master
>
> In addition
Hi Shawn,
On 20/09/14 20:58, Shawn Sörbom wrote:
> Hi,
> when I try to use gbp-create-remote-repo for my Debian package I get the
> following error:
>
> gbp-create-remote-repo --remote-url-pattern=ssh://github.com/shsorbom/kcm-ufw-
> debian.git gbp:
> info: Shall I create a repository for 'kcm-u
Hi,
when I try to use gbp-create-remote-repo for my Debian package I get the
following error:
gbp-create-remote-repo --remote-url-pattern=ssh://github.com/shsorbom/kcm-ufw-
debian.git gbp:
info: Shall I create a repository for 'kcm-ufw' at
'ssh://github.com/shsorbom/kcm-ufw-debian.git' now? (y/n
6 matches
Mail list logo
