Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.maint.python > #16203
| From | Carsten Schoenert <c.schoenert@t-online.de> |
|---|---|
| Newsgroups | linux.debian.maint.python |
| Subject | Re: Moving default branch after project creation |
| Date | 2024-08-12 08:20 +0200 |
| Message-ID | <Jawzn-4shD-1@gated-at.bofh.it> (permalink) |
| References | <J8VBT-3p4M-3@gated-at.bofh.it> <J8VBT-3p4M-1@gated-at.bofh.it> <J92tH-3tk7-1@gated-at.bofh.it> <J94lP-3uxT-3@gated-at.bofh.it> <Jawzn-4shD-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
Am 10.08.24 um 00:01 schrieb Alexandru Mihail: > Thanks everyone for chiming in ! > Debates around the branch name aside, I still can't find out how to > access the Gitlab settings button to change the default to anything. > It's a permissions thing I think. When I access a project under my > personal namespace I see the settings button, all is well. Here, it's > just missing. I was able to create the project, of course. The structure of the tree hasn't changed since the last time i was looking into, did you read my previous email in detail? > $ git logg > * commit 4c0b559c9f60321be2fa412d73555ab38c517f16 (origin/pristine-tar) > Author: Alexandru Mihail <alexandru.mihail2897@gmail.com> > Date: Wed Aug 7 19:11:03 2024 +0300 > > pristine-tar data for psrecord_1.4.orig.tar.gz > > * commit 1443d1a19aeed367f2f2131757f01e2b9eafcfb4 (tag: upstream/1.4, origin/upstream, origin/debian/master, upstream) > | Author: Alexandru Mihail <alexandru.mihail2897@gmail.com> > | Date: Wed Aug 7 18:46:41 2024 +0300 > | > | New upstream version 1.4 > | > * commit 4c41bddf5c750a5c694aaba42c8252b444856ff7 (HEAD -> main, origin/main, origin/HEAD) > Author: Alexandru Mihail <alexandru.mihail2897@gmail.com> > Date: Wed Aug 7 15:21:38 2024 +0000 > > Initial commit The structure of the tree is simply wrong, given you are at the beginning I suggest to drop the current tree and restart from scratch within your namespace. For me it makes no sense to work further on that base. It make things unnecessary harder. Once it's working on your side it's easy to push then the tree to the repo on the DPT in Salsa again. -- Regards Carsten
Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: Moving default branch after project creation Julian Gilbey <julian@d-and-j.net> - 2024-08-07 22:40 +0200
Re: Moving default branch after project creation Nicholas D Steeves <sten@debian.org> - 2024-08-08 01:00 +0200
Re: Moving default branch after project creation Carsten Schoenert <c.schoenert@t-online.de> - 2024-08-08 06:00 +0200
Re: Moving default branch after project creation Julian Gilbey <julian@d-and-j.net> - 2024-08-08 08:00 +0200
Re: Moving default branch after project creation Carsten Schoenert <c.schoenert@t-online.de> - 2024-08-08 09:00 +0200
Re: Moving default branch after project creation Martin <debacle@debian.org> - 2024-08-08 09:50 +0200
Re: Moving default branch after project creation Carsten Schoenert <c.schoenert@t-online.de> - 2024-08-08 13:10 +0200
Re: Moving default branch after project creation Carsten Schoenert <c.schoenert@t-online.de> - 2024-08-12 08:20 +0200
Re: Moving default branch after project creation Alexandru Mihail <alexandru.mihail2897@gmail.com> - 2024-08-12 09:40 +0200
csiph-web