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 say
On Thu, Oct 5, 2017 at 8:52 AM, Jose Miguel Gallas Olmedo <
jgallaso(a)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 tracked
1.1.x-dev tracked
AGPUSH-1047 tracked
AGPUSH-1149_enable_direct_access_grant tracked
AGPUSH-1299 tracked
AGPUSH-1368 tracked
AGPUSH-1368-CherryPick tracked
AGPUSH-1567 tracked
AGPUSH-2049 tracked
BOM_updates tracked
DIST_update tracked
FLAT_METRICS_1 tracked
GSOC_2017_kafka tracked
JDK8 tracked
KC_master_package_renamed tracked
LatestParent tracked
Logger tracked
SenderSnippetUpdates tracked
dimitraz-patch-1 tracked
firefox-variant tracked
gcm-topics tracked
hibernate.hbm2ddl tracked
jms-batching tracked
kafka-readme tracked
kafka-readme-1 tracked
kc_isolated tracked
master tracked
pr-template tracked
readme_apns_http/2 tracked
release-1.1.0 tracked
safari-push tracked
ux-revamp tracked
webpush-variant tracked
wizard_typop tracked
Cheers,
JOSE MIGUEL GALLAS OLMEDO
ASSOCIATE QE, mobile
Red Hat
<
https://www.redhat.com/>
M: +34618488633 <
http://redhatemailsignature-marketing.itos.redhat.com/>
<
https://red.ht/sig>
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
--
Matthias Wessendorf
blog:
http://matthiaswessendorf.wordpress.com/
twitter:
http://twitter.com/mwessendorf