Sure, go ahead!
usually a PR is only made from your own fork ;-) but sometimes that is not always followed rule, but it should be deleted if no longer needed...However, please keep the "GSOC_2017_kafka" branch, besides the already mentioned branches.Let's see what other sayOn Thu, Oct 5, 2017 at 8:52 AM, Jose Miguel Gallas Olmedo <jgallaso@redhat.com> wrote:______________________________Hi,I see that there are loads of branches pushed to the upstream repo that IMO shouldn't be there. I think branches should always belong to the forks, below is the list.Apart from 1.1.x-dev and master I would like to delete all branches, specially the ones that are 2 years old!What do you think about this?Remote branches:1.1.4.Final-rhmap-13.11 tracked1.1.x-dev trackedAGPUSH-1047 trackedAGPUSH-1149_enable_direct_access_grant tracked AGPUSH-1299 trackedAGPUSH-1368 trackedAGPUSH-1368-CherryPick trackedAGPUSH-1567 trackedAGPUSH-2049 trackedBOM_updates trackedDIST_update trackedFLAT_METRICS_1 trackedGSOC_2017_kafka trackedJDK8 trackedKC_master_package_renamed trackedLatestParent trackedLogger trackedSenderSnippetUpdates trackeddimitraz-patch-1 trackedfirefox-variant trackedgcm-topics trackedhibernate.hbm2ddl trackedjms-batching trackedkafka-readme trackedkafka-readme-1 trackedkc_isolated trackedmaster trackedpr-template trackedreadme_apns_http/2 trackedrelease-1.1.0 trackedsafari-push trackedux-revamp trackedwebpush-variant trackedwizard_typop trackedCheers,_________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev --Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
twitter: http://twitter.com/mwessendorf
_______________________________________________
aerogear-dev mailing list
aerogear-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev