to all Jamoma Git Committers

classic Classic list List threaded Threaded
5 messages Options
tap
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

to all Jamoma Git Committers

tap
I have spent some time in the past few days trying to clean up the dizzying mess of old branches and tags.

After pulling (on both JamomaMax and JamomaCore), please cd into the folders and run the following:

    script/cleanup.sh

If you do not, and then you do a push that includes tags it will re-pollute the whole repository all over again.  Please don't let that happen -- pull and run the script now.  Thanks!

Tim


------------------------------------------------------------------------------

_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: to all Jamoma Git Committers

Antoine Villeret
oups...
I may have pushed some commit before reading your mail...
sorry for the mess...

Antoine

--
do it yourself                      
http://antoine.villeret.free.fr

2015-08-30 18:00 GMT+02:00 Timothy Place <[hidden email]>:
I have spent some time in the past few days trying to clean up the dizzying mess of old branches and tags.

After pulling (on both JamomaMax and JamomaCore), please cd into the folders and run the following:

    script/cleanup.sh

If you do not, and then you do a push that includes tags it will re-pollute the whole repository all over again.  Please don't let that happen -- pull and run the script now.  Thanks!

Tim


------------------------------------------------------------------------------

_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel



------------------------------------------------------------------------------

_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: to all Jamoma Git Committers

Trond Lossius
Administrator
In reply to this post by tap
Thanks, Tim.

I have one question though: Do we want to tag JamomaCore when we make a new JamomaMax release? I particular if we do the shift to setting up JamomaCore as a submodule of JamomaMax, shouldn’t it then be sufficient that JamomaMax is tagged? After all we have to expect that Core will be used for different kinds of releases that all may have their own individual practise for how versions are numbered and when they are released.

I’d say that Jamoma Core should be tagged when we consider the library itself to have reached milestones.

Best,
Trond



> On 30 Aug 2015, at 18:00, Timothy Place <[hidden email]> wrote:
>
> I have spent some time in the past few days trying to clean up the dizzying mess of old branches and tags.
>
> After pulling (on both JamomaMax and JamomaCore), please cd into the folders and run the following:
>
>     script/cleanup.sh
>
> If you do not, and then you do a push that includes tags it will re-pollute the whole repository all over again.  Please don't let that happen -- pull and run the script now.  Thanks!
>
> Tim
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Jamoma-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/jamoma-devel


------------------------------------------------------------------------------
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel
tap
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: to all Jamoma Git Committers

tap
In reply to this post by Antoine Villeret
Hi Antoine -- No problems in this case.  Using the command line tags are only pushed when the --tags options is specified.  Using various GUI apps it is much less predictable depending on how "smart" they try to be.

Tim


On Sun, Aug 30, 2015 at 1:18 PM, Antoine Villeret <[hidden email]> wrote:
oups...
I may have pushed some commit before reading your mail...
sorry for the mess...

Antoine

--
do it yourself                      
http://antoine.villeret.free.fr

2015-08-30 18:00 GMT+02:00 Timothy Place <[hidden email]>:
I have spent some time in the past few days trying to clean up the dizzying mess of old branches and tags.

After pulling (on both JamomaMax and JamomaCore), please cd into the folders and run the following:

    script/cleanup.sh

If you do not, and then you do a push that includes tags it will re-pollute the whole repository all over again.  Please don't let that happen -- pull and run the script now.  Thanks!

Tim


------------------------------------------------------------------------------

_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel



------------------------------------------------------------------------------

_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel



------------------------------------------------------------------------------

_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel
tap
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: to all Jamoma Git Committers

tap
In reply to this post by Trond Lossius
Yes, Trond, I agree.

BTW, thanks for all your efforts these past few days on the BEK server.  It's nice to have jamoma.org and friends back again, and I know that wasn't easy...


Tim


On Sun, Aug 30, 2015 at 1:58 PM, Trond Lossius <[hidden email]> wrote:
Thanks, Tim.

I have one question though: Do we want to tag JamomaCore when we make a new JamomaMax release? I particular if we do the shift to setting up JamomaCore as a submodule of JamomaMax, shouldn’t it then be sufficient that JamomaMax is tagged? After all we have to expect that Core will be used for different kinds of releases that all may have their own individual practise for how versions are numbered and when they are released.

I’d say that Jamoma Core should be tagged when we consider the library itself to have reached milestones.

Best,
Trond



> On 30 Aug 2015, at 18:00, Timothy Place <[hidden email]> wrote:
>
> I have spent some time in the past few days trying to clean up the dizzying mess of old branches and tags.
>
> After pulling (on both JamomaMax and JamomaCore), please cd into the folders and run the following:
>
>     script/cleanup.sh
>
> If you do not, and then you do a push that includes tags it will re-pollute the whole repository all over again.  Please don't let that happen -- pull and run the script now.  Thanks!
>
> Tim
>
> ------------------------------------------------------------------------------
> _______________________________________________
> Jamoma-devel mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/jamoma-devel


------------------------------------------------------------------------------
_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel


------------------------------------------------------------------------------

_______________________________________________
Jamoma-devel mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/jamoma-devel
Loading...