Strange git repo

Have a great idea for extending Zimbra? Share ideas, ask questions, contribute, and get feedback.
10119metux
Advanced member
Advanced member
Posts: 75
Joined: Sat Sep 13, 2014 2:29 am

Strange git repo

Postby 10119metux » Thu Mar 06, 2014 4:31 am

Hi folks,


while pulling the source via git, I've noticed the history (branch: ironmaiden-foss)

completely changed, compared to last pull from Feb. 6th - the branches diverged

on 3098 (!!!) commits.
And when picking the corresponding commit from new branch which matches

timestamp and message of the old head from my last pull, the trees also differ.
What are you folks doing ?!
By the way: why aren't there any tags for the existing releases ?
I hope you are aware that such things aren't actually helpful for getting any

contributions ... ;-o


cu


User avatar
quanah
Zimbra Alumni
Zimbra Alumni
Posts: 1667
Joined: Fri Sep 12, 2014 10:33 pm
Contact:

Strange git repo

Postby quanah » Thu Mar 06, 2014 5:55 am

Hi,
Due to an error in the mapping between perforce and git, several of the original repos had to be rebuilt.
As for releases: Releases are always done in their own branch, not as a tag to an existing branch. I.e., ironmaiden-foss is a development tree of whatever the next 8.0 release will be. ironmaiden-806-foss is the repository for the 8.0.6 release, ironmaiden-805-foss is the repository for the 8.0.5 release, etc. So if you want to look at what's being currently developed, you grab the development repository for that code line (helix-foss, ironmaiden-foss, main, etc). If you want the code for a specific release, then you grab the repository for that release.
Hope that helps,

Quanah
--Quanah
--
Quanah Gibson-Mount
Product Architect, Symas http://www.symas.com/
OpenLDAP Core team http://www.openldap.org/project/
10119metux
Advanced member
Advanced member
Posts: 75
Joined: Sat Sep 13, 2014 2:29 am

Strange git repo

Postby 10119metux » Thu Mar 06, 2014 12:52 pm

[quote user="quanah"]

As for releases: Releases are always done in their own branch, not as a tag to an existing branch.

[/QUOTE]
Why not ?

That's exactly what tags are meant for: assign a permanent name to a specific common

(= point in history), so we have the exact tree and the entire history which lead to that tree.
[quote user="quanah"]

I.e., ironmaiden-foss is a development tree of whatever the next 8.0 release will be. ironmaiden-806-foss is the repository for the 8.0.6 release, ironmaiden-805-foss is the repository for the 8.0.5 release, etc.

[/QUOTE]
Just had a look at them. Their histories have nothing in common - there's not even a

single point where the trees match. This renders the whole idea of branches pretty useless.


By the way: why do you still stick with that utterly complex, slow and expensive

(even *worse* that vss/tfs !) tool, which conceptionally still remains in the 80th,

at all ? Intellectual masochism ? Need to burn resources ? ;-o

Return to “Developers”

Who is online

Users browsing this forum: No registered users and 4 guests