Re: [DISCUSS] Renaming trunk to master

2015-02-10 Thread Jean-Baptiste Onofré
+1 Regards JB On 01/05/2015 07:27 PM, Hadrian Zbarcea wrote: It's a bit confusing, a leftover from the svn days. I think the rename was supposed to happen but it was somehow overlooked. Any objection to rename? Hadrian -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net

Re: [HEADS-UP][DISCUSS] Renaming trunk to master

2015-02-09 Thread artnaseef
Thank you Hadrian. -- View this message in context: http://activemq.2283324.n4.nabble.com/DISCUSS-Renaming-trunk-to-master-tp4689494p4691265.html Sent from the ActiveMQ - Dev mailing list archive at Nabble.com.

Re: [HEADS-UP][DISCUSS] Renaming trunk to master

2015-02-08 Thread Hadrian Zbarcea
Hi, I created the master branch myself. INFRA-9111 is still open. I don't have the karma to remove the 'trunk' branch. Please use 'master' from now on. Let's follow the commits to trunk and merge them to master, make sure nothing gets lost. Cheers, Hadrian On 02/03/2015 04:14 PM, Hadrian

[HEADS-UP][DISCUSS] Renaming trunk to master

2015-02-03 Thread Hadrian Zbarcea
Per agreement in this thread, now that 5.11.0 is out, I sent a request to infra [1] to rename trunk to master. Please keep an eye on it so you don't loose work. Cheers, Hadrian [1] https://issues.apache.org/jira/browse/INFRA-9111 On 01/06/2015 07:58 AM, Dejan Bosanac wrote: +1 Maybe we

Re: [DISCUSS] Renaming trunk to master

2015-01-06 Thread James Carman
+1, master is the norm, no matter which Git workflow you use. On Mon, Jan 5, 2015 at 1:27 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: It's a bit confusing, a leftover from the svn days. I think the rename was supposed to happen but it was somehow overlooked. Any objection to rename?

Re: [DISCUSS] Renaming trunk to master

2015-01-06 Thread Robbie Gemmell
+1 for the rename. Using master is typical and this is definitely a change now made by infra during migrations, based on experience of migrating a couple of things into Git repos at Qpid recently. On 5 January 2015 at 18:27, Hadrian Zbarcea hzbar...@gmail.com wrote: It's a bit confusing, a

Re: [DISCUSS] Renaming trunk to master

2015-01-06 Thread Dejan Bosanac
+1 Maybe we should wait with the rename until we have 5.11.0 released (there’s some work involved like reconfiguring jenkins and stuff, so it'll delay release) Regards -- Dejan Bosanac -- Red Hat, Inc. dbosa...@redhat.com Twitter: @dejanb Blog: http://sensatic.net ActiveMQ in

Re: [DISCUSS] Renaming trunk to master

2015-01-05 Thread Jim Gomes
I don't really know the conventions of git, but are the branches still called branches, or are they servants? Trunk/branches is a consistent metaphor. Master/branches is mixing metaphors. On Mon, Jan 5, 2015, 1:52 PM Timothy Bish tabish...@gmail.com wrote: +1 On 01/05/2015 01:27 PM, Hadrian

Re: [DISCUSS] Renaming trunk to master

2015-01-05 Thread Jaromir Hamala
AFAIK there is no distinction between trunk and branches in GIT. One of the branches just happens to be called master. On Mon, Jan 5, 2015 at 11:33 PM, Jim Gomes e.se...@gmail.com wrote: I don't really know the conventions of git, but are the branches still called branches, or are they

Re: [DISCUSS] Renaming trunk to master

2015-01-05 Thread Claus Ibsen
+1 On Mon, Jan 5, 2015 at 7:27 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: It's a bit confusing, a leftover from the svn days. I think the rename was supposed to happen but it was somehow overlooked. Any objection to rename? Hadrian -- Claus Ibsen - Red Hat, Inc.

[DISCUSS] Renaming trunk to master

2015-01-05 Thread Hadrian Zbarcea
It's a bit confusing, a leftover from the svn days. I think the rename was supposed to happen but it was somehow overlooked. Any objection to rename? Hadrian

Re: [DISCUSS] Renaming trunk to master

2015-01-05 Thread Hiram Chirino
+1 for doing the rename. On Mon, Jan 5, 2015 at 1:27 PM, Hadrian Zbarcea hzbar...@gmail.com wrote: It's a bit confusing, a leftover from the svn days. I think the rename was supposed to happen but it was somehow overlooked. Any objection to rename? Hadrian -- Hiram Chirino Engineering |