1) Our coding methods do not support the github model - We use long lines of tab spaced coding; github does better with multi-line objects
2) PrettyLST usage pretty much foobars the order of objects and can cause havoc for any merging by other users
Nylanfs wrote:When editing a large set like the rsrd or pathfinder having an object on one line and then having all the same tags line up are fairly important to me.
henkslaaf wrote:So the topic of having all objects described on a single line is actually not very much related to Git. It is related to merging.
What does it have to do with git?
Now why does this come up during the Git discussion?
1) Partly because I brought these up one after the other. I think that multi-line objects would be an improvement for our SVN workflow anyway.
2) We will be merging MUCH more often when using Git. Look at the release strategy Andrew has top-of-mind. We could do all sorts of cool stuff that are hard to do in SVN. Like just cherry-picking a patch to the 6.2 branch. Easy, but not with multi-line objects.
henkslaaf wrote:Nylanfs wrote:When editing a large set like the rsrd or pathfinder having an object on one line and then having all the same tags line up are fairly important to me.
Yeah, there are bound to be use-cases. Just wondering which ones. I have a vim plugin that transforms from single-line to multi-line when opening the file, I've never missed it.
Just out of curiosity: what file editor are you using?
LegacyKing wrote:henkslaaf wrote:So the topic of having all objects described on a single line is actually not very much related to Git. It is related to merging.
What does it have to do with git?
Now why does this come up during the Git discussion?
1) Partly because I brought these up one after the other. I think that multi-line objects would be an improvement for our SVN workflow anyway.
2) We will be merging MUCH more often when using Git. Look at the release strategy Andrew has top-of-mind. We could do all sorts of cool stuff that are hard to do in SVN. Like just cherry-picking a patch to the 6.2 branch. Easy, but not with multi-line objects.
Was that meant to be 'Easy, but not without multi-line objects.' Otherwise, it seems like you're arguing against multi-line...
LegacyKing wrote:Only issue with the split proposed is this:
I would also point out, whenever it's been possible, I have used the MOVE feature, and the RENAME feature. SVN has messed up and caused me to use the alternatives, but that has been the exception rather than the rule.
LegacyKing wrote:Only issue with the split proposed is this:
A split that is the most logical is these three:
[list=]
[*]Content
[*]PCGen - proper (All our IDEs are geared to use this)
[*]Utilities
[/list]
Content - includes NFD, our publisher docs, and our OOC materials.
PCGen - is the main program and should not be split up
Utilities - is our holding tank for practical aids to coding.
Return to Developers - Code Monkeys
Users browsing this forum: No registered users and 0 guests