Follow-up Comment #2, sr #111372 (group administration): What I would like to do is to delete the "master" branch and rename another branch, namely "new_parser_a", to "master" or "main" or something like that. I don't think this would be a problem with Git itself, but I thought it was possible that Savannah handled "master" branches in a special way. Therefore I wanted to see if I could find anything about this on the administration page. I've never used it for administering the repository, I just use Emacs' VC interface and sometimes commands on the command-line and have never done anything out of the ordinary.
I don't think it would be worth changing the name of the project just to have
access to the web interface for administering the repository.
There are hundreds of files and the content of most of them is identical
between the two branches. However, I just updated the copyright notices in
many of them, probably a couple of hundred, and so they are different from
the point of view of Git.
I could merge them using the "ort" strategy with the "theirs" option, but that
seems rather pointless since I just want to make the "new_parser_a" branch the
default one and get rid of the current "master". I also think there's a
chance that merging could fail disasterously.
If it's a problem, I'll just copy files and directories carefully into the
hierarchy I use for "master" and check them in. I've checked out the two
branches into two separate directory structures and never switch branches in
either one. Copying and checking in also seems prone to things going wrong,
but still safer than trying to merge the branches automatically.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/support/?111372>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
