[DONE] Clean up repo branches?

Started by Marsu42, September 26, 2013, 12:04:14 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

Marsu42

Currently there are 32 branches in the main ml repo - how about deleting the outdated branches?

They are dragged around with every fork which doesn't seem very clean & might create confusion as unified seems to be the only one being worked on... since there are so many ml working forks probably doing in-repo branches except for quick experiments isn't such a good idea at all, but create a full fork even if the person has write access to the main repo?

a1ex


Marsu42

Quote from: a1ex on September 26, 2013, 12:12:32 PM
+1

in this case, +1 for you just doing it :-> ... maybe after creating a zip backup of the branches if someone later on complains about something missing.

a1ex


dmilligan

Quote from: Marsu42 on September 26, 2013, 12:33:43 PM
maybe after creating a zip backup of the branches if someone later on complains about something missing.
you don't need to, this is version control, they will always be there even if you delete them, that's the whole point of version control

Marsu42

Quote from: dmilligan on September 26, 2013, 12:48:20 PM
you don't need to, this is version control, they will always be there even if you delete them, that's the whole point of version control

You're saying it's impossible to actually delete a branch on bitbucket, it's only logically removed but the data will remain there just like your embarrassing teen party snaps on facebook?

dmilligan

that's version control ;)

everything you do is computed as a change (diff) from the previous version and only the change is stored, hence the name 'changeset' a reposity is simply a huge list of changes, you apply them all and end up with the current version, even deleting is stored as a 'change'. you can always leave out a changeset or stop at an old version

I think something like this should work:

$ hg commit --close-branch -m "closed this branch"


Marsu42

Quote from: dmilligan on September 26, 2013, 01:00:34 PM
you apply them all and end up with the current version, even deleting is stored as a 'change'.

*If* you apply them - is is also true for a branch that went nowhere & wasn't merged with anything?

dmilligan


Marsu42