03-03-2018, 10:10 AM,
(This post was last modified: 03-03-2018, 11:16 AM by TurboPT.)
|
|
TurboPT
Administrator
      
|
Posts: 727
Threads: 10
Joined: Jun 2012
|
|
RE: Sourceforge subversion problem
Andy, we will eventually remove those entries with other future commits.
However, I don't believe that having that $Id reference would makes much sense in a distributed repository? (vs. centralized, like SVN)
They way that changes can be pulled (or not) across various repositories, at different/various points, I don't know how the $Id would be useful in the 'git realm'?
However, on the flip-side of that, there is history with every file, even across forks.
Just another mindset difference, I guess?
I see that git does have the concept of tagging (kinda reminds me of CVS in a way), but I don't yet have the perspective as to how useful these might be, or not.
|
|
03-03-2018, 01:52 PM,
(This post was last modified: 03-03-2018, 01:54 PM by phil.)
|
|
phil
Administrator
      
|
Posts: 1,239
Threads: 14
Joined: Jan 2012
|
|
RE: Sourceforge subversion problem
LOL!
Yes way overSEDous ... still a battle for my old head to get around the concepts as Andy noted - it is mind altering but sadly does seem to add about 5 steps over SVN to my usual workflow - at least it seems to work.
It was just a simple
Code: $svn commit -m 'some changes'
but now we have
Code: $commit -am 'some changes'
$push
then it is only on my own repository and I have to go into my browser to my repository on github then create a pull request on webERP-team and pull these changes into the master on webERP-team
The pull request then has to be merged into the webERP-team/master
... then I have to pull back down into my local repository
Phew .... it seems quite convoluted!!!
Am I making a meal of this, or is this how it is?
Phil Daintree
webERP Admin
Logic Works Ltd
http://www.logicworks.co.nz
|
|
|