why are there two trunks in PloneGetPaid?
|
View:
New views
5 Messages
—
Rating Filter:
Alert me
|
 |
why are there two trunks in PloneGetPaid?
by Brandon Craig Rhodes
::
Rate this Message:
This is probably my ignorance of Plone best practices showing through, but a quick Google search didn't turn up a good document on the layout of a Plone product in a Subversion source repository, so I'll ask here: why are there two trunks in the Products.PloneGetPaid repository? In fact, the repository seems to contain no fewer than four entire copies of the source code, named: 1. src/Products.PloneGetPaid/Products/PloneGetPaid/ 2. src/Products.PloneGetPaid/src/Products/PloneGetPaid/ 3. src/Products.PloneGetPaid/src/trunk/Products/PloneGetPaid/ 4. src/Products.PloneGetPaid/trunk/Products/PloneGetPaid/ It seems to be the base copy, that has neither "src", "src/trunk", nor "trunk" in front of it, that gets used in "getpaid.buildout". Why the two trunks? -- Brandon Craig Rhodes brandon@... http://rhodesmill.org/brandon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to getpaid-dev@... To unsubscribe from this group, send email to getpaid-dev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: why are there two trunks in PloneGetPaid?
by Michael Dunstan
::
Rate this Message:
On Tue, Aug 18, 2009 at 11:33 PM, Brandon Craig Rhodes<brandon@...> wrote: > > This is probably my ignorance of Plone best practices showing through, > but a quick Google search didn't turn up a good document on the layout > of a Plone product in a Subversion source repository, so I'll ask here: > why are there two trunks in the Products.PloneGetPaid repository? > > In fact, the repository seems to contain no fewer than four entire > copies of the source code, named: > > 1. src/Products.PloneGetPaid/Products/PloneGetPaid/ > 2. src/Products.PloneGetPaid/src/Products/PloneGetPaid/ > 3. src/Products.PloneGetPaid/src/trunk/Products/PloneGetPaid/ > 4. src/Products.PloneGetPaid/trunk/Products/PloneGetPaid/ > > It seems to be the base copy, that has neither "src", "src/trunk", nor > "trunk" in front of it, that gets used in "getpaid.buildout". > > Why the two trunks? I've bumped into that in the past and never figured out what that is all about either. I guess that it's some side effect from either miss placed commits or moving things around in the repository. And it should be cleaned up. I vote - Keep 1. Delete 2, 3 and 4. -- Michael Dunstan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to getpaid-dev@... To unsubscribe from this group, send email to getpaid-dev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: why are there two trunks in PloneGetPaid?
by Brandon Craig Rhodes
::
Rate this Message:
Michael Dunstan <michael.dunstan@...> writes: > On Tue, Aug 18, 2009 at 11:33 PM, Brandon Craig > Rhodes<brandon@...> wrote: > >> 1. src/Products.PloneGetPaid/Products/PloneGetPaid/ >> 2. src/Products.PloneGetPaid/src/Products/PloneGetPaid/ >> 3. src/Products.PloneGetPaid/src/trunk/Products/PloneGetPaid/ >> 4. src/Products.PloneGetPaid/trunk/Products/PloneGetPaid/ > > I vote - Keep 1. Delete 2, 3 and 4. And there I'd thought it was some clever scheme whose point I could not fathom. :-) Looking more closely, it appears that "/trunk/" was created by some sort of crime dog back in June, and has not been touched since then: ------------------------------------------------------------------------ r2705 | mcgruff.scruff@... | 2009-06-25 14:43:02 -0400 (Thu, 25 Jun 2009) | 1 line Merge VariableAmountDonationsBranch r2275:2394 to trunk ------------------------------------------------------------------------ Oddly enough, that branch already seems to have been merged into the project by "larubbio" in r2396 back in March, so I am not sure what was intended here. In any case, I have removed the directory from the project HEAD. Similarly, the "src/trunk" directory seems to have been created by exactly the same crime dog in r2706, but in that case he was not even kind enough to leave a commit message: ------------------------------------------------------------------------ r2706 | mcgruff.scruff@... | 2009-06-25 15:20:38 -0400 (Thu, 25 Jun 2009) | 1 line ------------------------------------------------------------------------ I have deleted that directory with the same extreme prejudice that I showed the first one. And, wow, the whole "/src/" directory itself was created by that same r2706 that I quoted above! A single commit managed to create two concentric copies of the project inside of the project itself, meaning that each file existed in three separate instances, one directory deeper than the next. That's really something. "Bahleeted," as Strong Bad would say. Ahhhh. Now searches of the source code tree are only returning one instance of each class and function defined in PloneGetPaid, rather than four. :-) I can continue exploring now. -- Brandon Craig Rhodes brandon@... http://rhodesmill.org/brandon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to getpaid-dev@... To unsubscribe from this group, send email to getpaid-dev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: why are there two trunks in PloneGetPaid?
by Lucie Lejard-2
::
Rate this Message:
Thank you for cleaning! Lucie -- six feet up, inc. | "Nowhere to go but open source" Direct Line +1 (317) 861-5948 x605 http://www.sixfeetup.com | Zope/Plone Custom Development + Hosting On Tue, Aug 18, 2009 at 8:03 AM, Brandon Craig Rhodes<brandon@...> wrote: > > Michael Dunstan <michael.dunstan@...> writes: > >> On Tue, Aug 18, 2009 at 11:33 PM, Brandon Craig >> Rhodes<brandon@...> wrote: >> >>> 1. src/Products.PloneGetPaid/Products/PloneGetPaid/ >>> 2. src/Products.PloneGetPaid/src/Products/PloneGetPaid/ >>> 3. src/Products.PloneGetPaid/src/trunk/Products/PloneGetPaid/ >>> 4. src/Products.PloneGetPaid/trunk/Products/PloneGetPaid/ >> >> I vote - Keep 1. Delete 2, 3 and 4. > > And there I'd thought it was some clever scheme whose point I could not > fathom. :-) > > Looking more closely, it appears that "/trunk/" was created by some sort > of crime dog back in June, and has not been touched since then: > > ------------------------------------------------------------------------ > r2705 | mcgruff.scruff@... | 2009-06-25 14:43:02 -0400 (Thu, 25 > Jun 2009) | 1 line > > Merge VariableAmountDonationsBranch r2275:2394 to trunk > ------------------------------------------------------------------------ > > Oddly enough, that branch already seems to have been merged into the > project by "larubbio" in r2396 back in March, so I am not sure what was > intended here. In any case, I have removed the directory from the > project HEAD. > > Similarly, the "src/trunk" directory seems to have been created by > exactly the same crime dog in r2706, but in that case he was not even > kind enough to leave a commit message: > > ------------------------------------------------------------------------ > r2706 | mcgruff.scruff@... | 2009-06-25 15:20:38 -0400 (Thu, 25 > Jun 2009) | 1 line > > > ------------------------------------------------------------------------ > > I have deleted that directory with the same extreme prejudice that I > showed the first one. > > And, wow, the whole "/src/" directory itself was created by that same > r2706 that I quoted above! A single commit managed to create two > concentric copies of the project inside of the project itself, meaning > that each file existed in three separate instances, one directory deeper > than the next. That's really something. > > "Bahleeted," as Strong Bad would say. > > Ahhhh. Now searches of the source code tree are only returning one > instance of each class and function defined in PloneGetPaid, rather than > four. :-) I can continue exploring now. > > -- > Brandon Craig Rhodes brandon@... http://rhodesmill.org/brandon > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to getpaid-dev@... To unsubscribe from this group, send email to getpaid-dev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
Re: why are there two trunks in PloneGetPaid?
by Michael Dunstan
::
Rate this Message:
On Wed, Aug 19, 2009 at 12:03 AM, Brandon Craig Rhodes<brandon@...> wrote: > "Bahleeted," as Strong Bad would say. That made my day. -- Michael Dunstan --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "getpaid-dev" group. To post to this group, send email to getpaid-dev@... To unsubscribe from this group, send email to getpaid-dev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/getpaid-dev?hl=en -~----------~----~----~----~------~----~------~--~--- |
| Free embeddable forum powered by Nabble | Forum Help |
