The ASF board is expanding the use of GIT, in the trial group for the
ASF. Do we want to take the plunge?
Carl.
-
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscr
What benefit is there to using git?
> -Original Message-
> From: Carl Trieloff [mailto:cctriel...@redhat.com]
> Sent: Monday, November 28, 2011 3:38 PM
> To: dev@qpid.apache.org
> Subject: GIT
>
>
> The ASF board is expanding the use of GIT, in the trial group f
it is a lot easier to merge features, and work with others on changes.
Carl.
On 11/28/2011 04:19 PM, Steve Huston wrote:
> What benefit is there to using git?
>
>> -Original Message-
>> From: Carl Trieloff [mailto:cctriel...@redhat.com]
>> Sent: Monday, Novembe
I would probably be quite happy just letting other projects play
guinea pig initially. I know a lot of the existing committers
(including me) already use git-svn and have done for years, which gets
you many of the benefits whilst letting those who need/want to use SVN
directly just keep doing so
Working with both, I've found "git pull" to be *much* faster than "svn
update". It's also much easier to specify which changed files you want
committed/posted. That said, they're both good. If you don't want the
full jump to Git perhaps Qpid can practi
As Robbie mentioned, most of the git fans are already using git-svn
(I'm one of them).
So we could perhaps wait for a bit to see how the trial unfolds.
My concern is, that not everybody may be ready to use git at this
point, so if we switch, then we will be disrupting the work for some
I have been using git for years now with Qpid, by cloning off the git
mirror and then use git-svn going foward (as per
http://wiki.apache.org/general/GitAtApache). I dont really do enough
updates to care much about the performance difference I must admit,
just the local branching and commits. I
After some more discussion, let's take a straw poll. I know many people
are using git already. If "many" accounts for most of our contributors,
we should really consider making the transition.
On Mon, 28 Nov 2011, Rajith Attapattu wrote:
As Robbie mentioned, most of t
I would look closest at the ones that arent using it to see why they
cant or dont want to, and base the decision largely on that. For the
many already using it, do they care about the bits we dont currently
get through lack of direct git write access?
Robbie
On 28 November 2011 22:28, Justin
Sorry, Rajith. Obviously, I agree!
On Mon, 28 Nov 2011, Justin Ross wrote:
After some more discussion, let's take a straw poll. I know many people are
using git already. If "many" accounts for most of our contributors, we
should really consider making the transition.
On M
I'm of the "if it ain't broke, don't fix it" persuasion and I don't have
any problem with svn. In the beginning of my Qpid work before I had svn
access I used git and I was happy to be able to leave it behind - I just
never quite got the way it works maybe.
I'd
On Mon, Nov 28, 2011 at 05:28:27PM -0500, Justin Ross wrote:
> After some more discussion, let's take a straw poll. I know many
> people are using git already. If "many" accounts for most of our
> contributors, we should really consider making the transition.
+1
On Mon, 2011-11-28 at 21:56 +, Robbie Gemmell wrote:
> I would probably be quite happy just letting other projects play
> guinea pig initially. I know a lot of the existing committers
> (including me) already use git-svn and have done for years, which gets
> you many of the ben
On 11/28/2011 05:38 PM, Robbie Gemmell wrote:
I would look closest at the ones that arent using it to see why they
cant or dont want to, and base the decision largely on that. For the
many already using it, do they care about the bits we dont currently
get through lack of direct git write access
On 11/28/2011 05:28 PM, Justin Ross wrote:
After some more discussion, let's take a straw poll. I know many people are
using git already. If "many" accounts for most of our contributors, we should
really consider making the transition
So, I'm not a git user, though I dare say I could learn... but I must admit
that I'd prefer not to be part of the pilot group and wait for others to
sort out any issues encountered before we consider moving across...
therefore I'd personally be -1 for moving in the trial... but ok
A pilot has been done already, this is a wider group, so I would look at
it as do we want to be in the second wave of projects to GIT, or wait it
out.
from what I see infra has a solid handle on GIT from the projects that
have switched already
Carl.
On 11/30/2011 11:09 AM, Rob Godfrey wrote
ould look at
> it as do we want to be in the second wave of projects to GIT, or wait it
> out.
>
> from what I see infra has a solid handle on GIT from the projects that
> have switched already
>
> Carl.
>
>
> On 11/30/2011 11:09 AM, Rob Godfrey wrote:
> > So, I&#
On 11/30/2011 11:48 AM, Rob Godfrey wrote:
Is there any sort of info available on the implications of the move... e.g.
will we still easily be able to refer to the history for our current svn
repo?
All the history will carry over into git. Even personal git repo's have the full
histor
Is anyone using the git repo? I have tried both methods on the source page
and I get the following errors:
$ git clone git://jukka.zitting.name/qpid.git qpid
Initialized empty Git repository in /var/data/build/tmp/qpid/.git/
fatal: read error (Connection reset by peer)
$ git clone http
On Wed, Oct 21, 2009 at 4:06 PM, Mike Owens wrote:
> Is anyone using the git repo? I have tried both methods on the source page
> and I get the following errors:
>
> $ git clone git://jukka.zitting.name/qpid.git qpid
> Initialized empty Git repository in /var/data/build/tmp/qpi
On Wed, Oct 21, 2009 at 4:30 PM, Aidan Skinner wrote:
> On Wed, Oct 21, 2009 at 4:06 PM, Mike Owens wrote:
>
>> Is anyone using the git repo? I have tried both methods on the source page
>> and I get the following errors:
>>
>> $ git clone git://jukka.zitting.nam
perfect. thanks.
On Wed, Oct 21, 2009 at 10:32 AM, Aidan Skinner wrote:
> On Wed, Oct 21, 2009 at 4:30 PM, Aidan Skinner
> wrote:
> > On Wed, Oct 21, 2009 at 4:06 PM, Mike Owens wrote:
> >
> >> Is anyone using the git repo? I have tried both methods on the sourc
See http://wiki.apache.org/general/GitAtApache. Works like a charm and very
quick to set up, took < 5min for me to do the whole lot. In fact cloning the git
repo with qpid's _entire history_ took about as long as an svn checkout of trunk!
Try it, you won't regret it.
+1
Aidan converted me to the ways of Git previously, and I'd have been
rather stuck without it over the past 3-4 weeks (no internet access at
home, its
a bit busted and I'm being treated to a calamity of errors by the
phone company in trying to get it fixed).
On 2 Jul 2009
On Thu, Jul 2, 2009 at 11:03 PM, Alan Conway wrote:
> See http://wiki.apache.org/general/GitAtApache. Works like a charm and very
> quick to set up, took < 5min for me to do the whole lot. In fact cloning the
> git repo with qpid's _entire history_ took about as long as an svn ch
[IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
Hello Apache projects,
I am writing to you because you may have git repositories on the
git-wip-us server, which is slated to be decommissioned in the coming
ReviewBoard is a tool for reviewing patches before they are comitted. Apache
hosts it at https://reviews.apache.org/ and there is a qpid group. I've done one
review so far, the tool seems useful. If you want to get a patch reviewed I
suggest trying it.
If you use git-svn then the att
Qpid
checkins having a related JIRA isuue number in the checkin log precisely
to enable our tracking.
Is there currently a plan to bring back the subversion integration?
Alternatively I think we would be perfectly happy with an integration
with the git mirror of the repository if that is easier.
If
I'm totally in love with git, and I think you should be too. I think
it's particularly useful for non-comitters, since it allows local
commits and branches which should make tracking trunk easier. git
format-patch makes getting your changes into a jira-able format a
doodle.
Here's
$ git clone git://git.apache.org/qpid.git
Cloning into 'qpid'...
fatal: read error: Connection reset by peer
Can someone look into this?
--
Regards, Irina.
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apac
Given that there seems to be interest in moving the qpid-dispatch source
repository to git, I'm calling a formal vote on the topic.
[ ] Yes - move the qpid-dispatch repo to git
[ ] No - no change: leave qpid-dispatch on subversion
thanks
[X ] Yes - move the qpid-dispatch repo to git
> -Original Message-
> From: Ken Giusti [mailto:kgiu...@redhat.com]
> Sent: Tuesday, August 04, 2015 10:06 AM
> To: Qpid Dev
> Subject: [VOTE] Move Dispatch to git
>
>
> Given that there seems to be interest in
lable via the Atlassian UPM we might consider that.
> But I have yet to see one.
Thanks for the clear explanation.
Is this also true for git integration? Is there git integration
available for JIRA (that we could potentially use)?
>
> There is *nothing* stopping you entering the JI
etrimental to the JIRA service. If someone finds a *good*
>> 3rd party plugin, available via the Atlassian UPM we might consider that.
>> But I have yet to see one.
>
> Thanks for the clear explanation.
>
> Is this also true for git integration? Is there git integrat
> was incredibly detrimental to the JIRA service. If someone finds a *good*
>> 3rd party plugin, available via the Atlassian UPM we might consider that.
>> But I have yet to see one.
>
> Thanks for the clear explanation.
>
> Is this also true for git integration? I
Qpid put in place a policy that led to most Qpid
checkins having a related JIRA isuue number in the checkin log precisely
to enable our tracking.
Is there currently a plan to bring back the subversion integration?
Alternatively I think we would be perfectly happy with an integration
with the git m
g a related JIRA isuue number in the checkin log precisely
> to enable our tracking.
>
> Is there currently a plan to bring back the subversion integration?
> Alternatively I think we would be perfectly happy with an integration
> with the git mirror of the repository if that is ea
On Fri, Jan 25, 2013 at 6:52 AM, Daniel Gruno wrote:
> 4) Use JIRA's REST API to post a comment in the appropriate JIRA ticket.
Will adding to the comment load like this speed the day when the ASF's
gigantic monolithic JIRA instance topples over from sheer size?
(The "JIRApocalypse"?)
Marvin H
>
> >> So until that situation is resolved we will not run that code again, as it
> >> was incredibly detrimental to the JIRA service. If someone finds a *good*
> >> 3rd party plugin, available via the Atlassian UPM we might consider that.
> >> But I have
http://status.apache.org/ shows things pretty normal.
I had to "git pull" twice to update my repo:
(trunk=5cdfd qpid/ build/ qpid/) > ~/git/qpid> git pull
fatal: unable to connect to git.apache.org:
git.apache.org[0: 54.84.58.65]: errno=Connection refused
1 (trunk=5
Yes, it is working now.
Thanks.
- Original Message -
From: "Chuck Rolke"
To: dev@qpid.apache.org
Sent: Monday, March 30, 2015 5:18:06 PM
Subject: Re: Problem with Qpid git mirror
http://status.apache.org/ shows things pretty normal.
I had to "git pull" twice to updat
On Mon, Mar 30, 2015 at 03:56:36PM -0400, Irina Boverman wrote:
> $ git clone git://git.apache.org/qpid.git
> Cloning into 'qpid'...
> fatal: read error: Connection reset by peer
>
> Can someone look into this?
Apparently the git/ssh interface is no longer available.
[X] Yes - move the qpid-dispatch repo to git
-
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
[+1] Yes - move the qpid-dispatch repo to git
On 4 August 2015 at 15:06, Ken Giusti wrote:
>
> Given that there seems to be interest in moving the qpid-dispatch source
> repository to git, I'm calling a formal vote on the topic.
>
> [ ] Yes - move the qpid-dispatch repo
+1 [X] Yes - move the qpid-dispatch repo to git
--
Tim Bish
Sr Software Engineer | RedHat Inc.
tim.b...@redhat.com | www.redhat.com
twitter: @tabish121
blog: http://timbish.blogspot.com/
-
To unsubscribe, e-mail: dev-unsubscr
We should move the code to git,
Any way you look at it.
It's the best code control system
So new and shiny that it glistens.
We should move it any day.
We should move it right away.
But one fact here we should construe.
When I say "We", I'm meaning "You".
:-)
[X
+1 [Yes]
On 08/04/2015 10:06 AM, Ken Giusti wrote:
Given that there seems to be interest in moving the qpid-dispatch source
repository to git, I'm calling a formal vote on the topic.
[ ] Yes - move the qpid-dispatch repo to git
[ ] No - no change: leave qpid-dispatch on subversion
t
Just a head's up - I'm on vacation next week, so I'll let this vote remain open
until I get back.
I'll close the vote on 8/17
- Original Message -
> Sent: Tuesday, August 4, 2015 10:06:14 AM
> Subject: [VOTE] Move Dispatch to git
>
>
> Given that t
Back from vacation!
I'll close the vote today at 5pm EDT and announce the results.
thanks,
-K
- Original Message -
> From: "Ken Giusti"
> To: "Qpid Dev"
> Sent: Friday, August 7, 2015 11:25:28 AM
> Subject: Re: [VOTE] Move Dispatch to git
>
&
+1 [Yes]
- Original Message -
> From: "Ken Giusti"
> To: dev@qpid.apache.org
> Sent: Monday, August 17, 2015 9:58:59 AM
> Subject: Re: [VOTE] Move Dispatch to git
>
> Back from vacation!
>
> I'll close the vote today at 5pm EDT and ann
he.org
> Sent: Monday, August 17, 2015 5:01:33 PM
> Subject: Re: [VOTE] Move Dispatch to git
>
> +1 [Yes]
>
>
> - Original Message -
> > From: "Ken Giusti"
> > To: dev@qpid.apache.org
> > Sent: Monday, August 17, 2015 9:58:59 AM
&g
Giusti"
>> To: dev@qpid.apache.org
>> Sent: Monday, August 17, 2015 5:01:33 PM
>> Subject: Re: [VOTE] Move Dispatch to git
>>
>> +1 [Yes]
>>
>>
>> - Original Message -
>> > From: "Ken Giusti"
>> > To: dev@qpi
Added a top level readme similar to Proton's.
The INFRA JIRA:
https://issues.apache.org/jira/browse/INFRA-10140
- Original Message -
> From: "Robbie Gemmell"
> To: dev@qpid.apache.org
> Sent: Monday, August 17, 2015 5:13:52 PM
> Subject: Re: [RESULT]
The website is out of date.
I fixed the main "Git repository" link but there are other links we
can't fix till we have a master branch. Please, please delete trunk (in
the git repo only) at the same time as creating master. Not finding
trunk is a momentary irritation, having bot
DOH! Pulled the trigger to fast, I see the git repo is still read-only.
Undoing my website change, my offer to help with website update stands
so I can redeem myself.
On Tue, 2015-08-18 at 16:34 -0400, aconway wrote:
> The website is out of date.
>
> I fixed the main "Git reposi
Sorry - INFRA is migrating right now. The new git repo is r/o until I give it
a thumbs up.
At this point, the git log of the old and new repos differ in the last 14
commits made. The Author field is different.
diff old new:
1,2c1,2
< commit a45d87dc03fe0fb48bc23821068967c3d861438c
<
Nevermind - that diff appears only in my git-svn repo tree.
When compared to http://git.apache.org/dispatch.git, there is no difference.
Waiting for INFRA to write enable the new repo...
- Original Message -
> From: "Ken Giusti"
> To: dev@qpid.apache.org
> Sent: Tuesd
Done. The new git repo for dispatch is open for business.
https://git-wip-us.apache.org/repos/asf/qpid-dispatch.git
- Original Message -
> From: "Ken Giusti"
> To: dev@qpid.apache.org
> Sent: Tuesday, August 18, 2015 5:13:56 PM
> Subject: Re: [RESULT] [VOTE
Hi Folks,
Per the below mail sent by the ASF Infrastructure team (to dev@), our Git
repositories will be migrated from the original/old git-wip-us service on to
the newer gitbox.apache.org service by February 7th.
This is definitely happening, but we have some say over when/how it does:
1
Qpid Devs,
I'm working with another developer (not an Apache committer) to write a
c++ API and some wrappers in Python and Ruby for the Qpid Management
Framework. This is a fairly substantial piece of work which will
benefit greatly from being able to share a code repository.
When it is rea
Good news everyone!
The migration of the java components from svn to git is now complete!
All history on trunk has been preserved.
The 6.x branches and tags have also been migrated.
Older branches and tags have not been migrated and remain in the svn
repository for the archaeologists amongst us
Show of hands: would any of the dispatch developers object to moving the
dispatch project from subversion to git?
I've been using the git-svn conduit with dispatch, and, well, it just feels
like a hack.
Sure, I'm personally biased towards git, and maybe there really isn't a s
Hi everybody,
I notice that nobody has contributed to the repository[1] maintained in
Debian and it may be easier to maintain the debian/sid branch in the
main qpid-proton repository[2]
Would you be happy to accept me as a committer in the project so I can
push the branch and any future changes
+1 - thanks for engaging this, Robbie.
> -Original Message-
> From: Robbie Gemmell
> Sent: Monday, December 10, 2018 11:10 AM
> To: us...@qpid.apache.org; dev@qpid.apache.org
> Subject: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
>
> Hi Folk
On Mon, 10 Dec 2018 at 17:10, Robbie Gemmell
wrote:
> Hi Folks,
>
> Per the below mail sent by the ASF Infrastructure team (to dev@), our Git
> repositories will be migrated from the original/old git-wip-us service on
> to
> the newer gitbox.apache.org service by Februar
On Mon, Dec 10, 2018 at 11:10 AM Robbie Gemmell
wrote:
> Hi Folks,
>
> Per the below mail sent by the ASF Infrastructure team (to dev@), our Git
> repositories will be migrated from the original/old git-wip-us service on
> to
> the newer gitbox.apache.org service by Februar
+1 from me for early migration too, albeit from my not-so-lofty status as a
very occasional committer :)
On Mon, 10 Dec 2018 at 16:10, Robbie Gemmell
wrote:
> Hi Folks,
>
> Per the below mail sent by the ASF Infrastructure team (to dev@), our Git
> repositories will be migra
+1 to migrate asap.
-Chuck
- Original Message -
> From: "Robbie Gemmell"
> To: us...@qpid.apache.org, dev@qpid.apache.org
> Sent: Monday, December 10, 2018 11:10:10 AM
> Subject: [NOTICE / DISCUSS] migrating Git repositories to gitbox.apache.org
>
> Hi Fo
ructure team (to dev@), our Git
> repositories will be migrated from the original/old git-wip-us service on to
> the newer gitbox.apache.org service by February 7th.
>
> This is definitely happening, but we have some say over when/how it does:
> 1. Document consensus on list and volunta
bsite.
Folks using the "git-wip-us" repositories will need to swap over to
pulling/pushing via the new locations, swapping "git-wip-us" for
"gitbox" in any existing URLs (such as in /.git/config).
The GitHub mirror URLs continue as before. Committers can now gain
write
ary
> details in the repos (updated broker-j master pom.xml as a starter),
> and updating the website.
>
> Folks using the "git-wip-us" repositories will need to swap over to
> pulling/pushing via the new locations, swapping "git-wip-us" for
> "gitbox" i
See e.g. those on
https://issues.apache.org/jira/browse/PROTON-1979.
It seems that a broken link in the form of
https://git-wip-us.apache.org/repos/asf?p=qpid-proton.git;h=5ba471d
can be rewritten to a working link
https://gitbox.apache.org/repos/asf?p=qpid-proton.git;a=commit;h=5ba471d
I
x27; on Feb
> 7th, unless they have actually all been migrated before then.
>
> Note that until that happens the adjustment needed for any old links
> like below is just changing the "git-wip-us" subdomain in the URL to
> "gitbox" since both are using the same web u
On Wed, Mar 18, 2009 at 7:13 PM, Ted Ross wrote:
> If anyone has any objections or concerns about this plan, please let me know
> as I do not wish to run afoul of the Qpid/ASF community.
This seems rather cumbersome and I wish there was a better way. :(
- Aidan
--
Apache Qpid - World Dominatio
Hello All,
We would like to notify all committers that we are starting the
svn to git migration of the Qpid Broker-J and Qpid JMS AMQP 0-x
components as discussed in [1].
Please do not commit to [2] and/or [3] or any subfolders until
further notice.
Kind regards,
Lorenz Quack
[1]
http://qpid
Thanks Lorenz and Alex for working on this, its really nice to have
all the components in their own Git repos now.
Robbie
On 25 April 2017 at 09:05, Lorenz Quack wrote:
> Good news everyone!
>
> The migration of the java components from svn to git is now complete!
>
> All histo
On 11/28/2014 01:42 PM, r...@apache.org wrote:
Repository: qpid-proton
Updated Branches:
refs/heads/master df970a8fd -> db437cf4a
removed alan's extraneous colon
Don't you need a medical license to do that?
-
To unsubscr
On 28/11/14 16:26, Gordon Sim wrote:
On 11/28/2014 01:42 PM, r...@apache.org wrote:
Repository: qpid-proton
Updated Branches:
refs/heads/master df970a8fd -> db437cf4a
removed alan's extraneous colon
Don't you need a medical license to do that?
--
On Sat, 2014-11-29 at 00:25 +, Fraser Adams wrote:
> On 28/11/14 16:26, Gordon Sim wrote:
> > On 11/28/2014 01:42 PM, r...@apache.org wrote:
> >> Repository: qpid-proton
> >> Updated Branches:
> >>refs/heads/master df970a8fd -> db437cf4a
> >>
> >>
> >> removed alan's extraneous colon
> >
>
+1, I'm up for it.
-Ted
On 07/31/2015 10:29 AM, Ken Giusti wrote:
Show of hands: would any of the dispatch developers object to moving the
dispatch project from subversion to git?
I've been using the git-svn conduit with dispatch, and, well, it just feels
like a hack.
Sure, I&#x
+1
It does clear like the development universe has decided that git
is the preferred technology. Then it's worth it just so that developers
on this project will not have to keep two different source code control
systems in their heads.
Also, I do _not_ think that git is just a fashion. I
Following up on this request, can anybody comment on this please?
I'd like to get the existing 0.22.0-1 package into Git and then proceed
to prepare a package of the latest version.
On 22/11/2018 15:04, Daniel Pocock wrote:
>
> Hi everybody,
>
> I notice that nobody has c
Hey, Daniel. Thanks for reaching out about this. We'd love to have a more
up to date Debian package.
Some questions:
On Thu, Dec 6, 2018 at 1:59 AM Daniel Pocock wrote:
> > I notice that nobody has contributed to the repository[1] maintained in
> > Debian and it may be easier to maintain the
On Thu, 6 Dec 2018 at 18:37, Justin Ross wrote:
>
> Hey, Daniel. Thanks for reaching out about this. We'd love to have a more
> up to date Debian package.
>
> Some questions:
>
> On Thu, Dec 6, 2018 at 1:59 AM Daniel Pocock wrote:
>
> > > I notice that nobody has contributed to the repository[1
tends to have a single spec file
- Debian requires a group of files and they always have to be in a
directory debian/*
Notice that what I do with other projects (e.g. reSIProcate) is create a
Git branch for each Debian build. So the debian/* directory is not
present at all in the master branch.
t
> > /packaging/debian. That's the pattern we have used for some
> > other Qpid components.
> >
>
> There is a major difference between Debian and Fedora:
>
> - Fedora tends to have a single spec file
>
> - Debian requires a group of files and they alway
Jiri Daněk created DISPATCH-2357:
Summary: Don't clone git tips in Dockerfile
Key: DISPATCH-2357
URL: https://issues.apache.org/jira/browse/DISPATCH-2357
Project: Qpid Dispatch
Issue
current upstream checkout.
> Don't clone git tips in Dockerfile
> --
>
> Key: DISPATCH-2357
> URL: https://issues.apache.org/jira/browse/DISPATCH-2357
> Project: Qpid Dispatch
>
[
https://issues.apache.org/jira/browse/DISPATCH-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk reassigned DISPATCH-2357:
Assignee: Jiri Daněk
> Don't clone git tips in Do
pull request, #1681:
URL: https://github.com/apache/qpid-dispatch/pull/1681
Built with
```
podman build .
```
Checked that qdrouterd starts up and that qdstat and qdmanage --help works.
> Don't clone git tips i
[
https://issues.apache.org/jira/browse/DISPATCH-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk updated DISPATCH-2357:
-
Affects Version/s: 1.19.0
> Don't clone git tips in Do
[
https://issues.apache.org/jira/browse/DISPATCH-2357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jiri Daněk updated DISPATCH-2357:
-
Fix Version/s: 1.20.0
> Don't clone git tips in Do
[
https://issues.apache.org/jira/browse/QPID-7640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7640:
-
Fix Version/s: (was: Future)
qpid-java-broker-7.0.0
> Migrate qpid-java svn to
[
https://issues.apache.org/jira/browse/QPID-7640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Keith Wall updated QPID-7640:
-
Component/s: (was: Java Client)
> Migrate qpid-java svn to
In addition to the issues needing fixed and thus requiring more time
to address (essentially checking out every revision of qpid-java code
from the svn repo's 1.8 million commits again, twice), there was some
discussion yesterday on IRC around the history in the new git repo for
the client
there was some
> discussion yesterday on IRC around the history in the new git repo for
> the client. The situation will be clearer once the new checkouts are
> complete, but anyone wanting to follow along before then can find the
> chat log on the associated JIRA at
> https://issue
Keith Wall created QPID-7640:
Summary: Migrate qpid-java svn to git
Key: QPID-7640
URL: https://issues.apache.org/jira/browse/QPID-7640
Project: Qpid
Issue Type: Task
Components: Java
the qpidversion.properties as it
includes the SVN revision number.
> Migrate qpid-java svn to git
> -
>
> Key: QPID-7640
> URL: https://issues.apache.org/jira/browse/QPID-7640
> Project: Qpid
>
.org
> Sent: Tuesday, July 7, 2015 3:50:16 PM
> Subject: [2/2] qpid-proton git commit: PROTON-928: cancellable tasks
>
> PROTON-928: cancellable tasks
>
> A scheduled task can be cancelled.
> A cancelled task does not prevent reactor from stopping running
>
>
> Pr
1 - 100 of 222 matches
Mail list logo
