Re: Commit deletion

Infra can for sure, locally it is not there anymore - that said as mentionned, here we sadly lost some commits but no "head" code. Le 6 déc. 2016 07:19, "Jean-Louis Monteiro" a écrit : You mean locally or on the server? I was wondering if Infra could help on this or not. JLouis -- Jean-Louis

Re: Commit deletion

You mean locally or on the server? I was wondering if Infra could help on this or not. JLouis -- Jean-Louis Monteiro http://twitter.com/jlouismonteiro http://www.tomitribe.com On Mon, Dec 5, 2016 at 7:39 PM, Shahim Essaid wrote: > Is using the git log files under .git/logs/* not an option for

Re: Commit deletion

Is using the git log files under .git/logs/* not an option for finding the needed SHAs? Git keeps all SHA changes for any branch in these files for some time (I think 30 days by default) so that the objects are not garbage collected. Any SHA in these files still counts as a reference to the git co

Re: authorization for ejbd/http client

2016-12-05 23:48 GMT+01:00 David Blevins : > > On Dec 5, 2016, at 10:29 AM, Romain Manni-Bucau > wrote: > > > > 2016-12-05 19:24 GMT+01:00 David Blevins : > > > >> > >>> On Dec 5, 2016, at 4:21 AM, Romain Manni-Bucau > >> wrote: > >>> > >>> Concretely the proposal can be: > >>> > >>> p.setProper

Re: authorization for ejbd/http client

On Mon, Dec 5, 2016 at 6:24 PM, David Blevins wrote: > > > On Dec 5, 2016, at 4:21 AM, Romain Manni-Bucau > wrote: > > > > Concretely the proposal can be: > > > > p.setProperty(Context.INITIAL_CONTEXT_FACTORY, > RemoteInitialContextFactory. > > class.getName()); > > p.setProperty(Context.PROVIDE

Re: authorization for ejbd/http client

> On Dec 5, 2016, at 10:29 AM, Romain Manni-Bucau wrote: > > 2016-12-05 19:24 GMT+01:00 David Blevins : > >> >>> On Dec 5, 2016, at 4:21 AM, Romain Manni-Bucau >> wrote: >>> >>> Concretely the proposal can be: >>> >>> p.setProperty(Context.INITIAL_CONTEXT_FACTORY, >> RemoteInitialContextFact

Re: authorization for ejbd/http client

2016-12-05 19:24 GMT+01:00 David Blevins : > > > On Dec 5, 2016, at 4:21 AM, Romain Manni-Bucau > wrote: > > > > Concretely the proposal can be: > > > > p.setProperty(Context.INITIAL_CONTEXT_FACTORY, > RemoteInitialContextFactory. > > class.getName()); > > p.setProperty(Context.PROVIDER_URL, ejbU

Re: Commit deletion

if you have the old history you can cherry pick it but guess we want to enforce the consistency with master instead of ensure 1.7 and 7.x forks - was actually one of the goal of the initial commit. Romain Manni-Bucau @rmannibucau | Blog

Re: Commit deletion

Is there a way to get the commit back? -- David Blevins http://twitter.com/dblevins http://www.tomitribe.com > On Dec 5, 2016, at 5:13 AM, Romain Manni-Bucau wrote: > > +1 > > note that if you have the history you can still get back the commits from > their hash (but for this one i lost them

Re: authorization for ejbd/http client

> On Dec 5, 2016, at 4:21 AM, Romain Manni-Bucau wrote: > > Concretely the proposal can be: > > p.setProperty(Context.INITIAL_CONTEXT_FACTORY, RemoteInitialContextFactory. > class.getName()); > p.setProperty(Context.PROVIDER_URL, ejbUrl + "?authype=basic"); > p.setProperty(Context.PRINCIPAL, "t

Re: Commit deletion

+1 note that if you have the history you can still get back the commits from their hash (but for this one i lost them and JL didnt have them but wanted to fix 1.7.x branch asap) Romain Manni-Bucau @rmannibucau | Blog | Old

Commit deletion

Raising this to the top level, as opposed to being inside another thread... We had have a git reset --hard HEAD^X issued against the tomee-1.7.x branch. The upshot is that although the commits in question are in the repository somewhere, they no longer show up in the history for that branch. This

Re: authorization for ejbd/http client

2016-12-05 12:56 GMT+01:00 Jonathan Gallimore : > On Mon, Dec 5, 2016 at 11:17 AM, Romain Manni-Bucau > > wrote: > > > Hi guys, > > > > Just a quite summary of last fixes we worked on with Jonathan regarding > the > > security for ejbd/http client: > > > > - we already have authorization paramet

Re: authorization for ejbd/http client

On Mon, Dec 5, 2016 at 11:17 AM, Romain Manni-Bucau wrote: > Hi guys, > > Just a quite summary of last fixes we worked on with Jonathan regarding the > security for ejbd/http client: > > - we already have authorization parameter in the provider url for months > (years now?). This was not removed

Re: today's git commits noise

2016-12-05 12:34 GMT+01:00 Jonathan Gallimore : > Ok, so effectively head of tomee-1.7.x got shifted back a number of commits > (git reset --hard HEAD^X, or something similar, right?). So those commits > are still there "somewhere" but not visible within tomee-1.7.x. Got it. A > revert may have g

Re: today's git commits noise

Ok, so effectively head of tomee-1.7.x got shifted back a number of commits (git reset --hard HEAD^X, or something similar, right?). So those commits are still there "somewhere" but not visible within tomee-1.7.x. Got it. A revert may have given us a bit of a clearer view in the history as to what

authorization for ejbd/http client

Hi guys, Just a quite summary of last fixes we worked on with Jonathan regarding the security for ejbd/http client: - we already have authorization parameter in the provider url for months (years now?). This was not removed from the url so the user needed to exclude some url from the access log i

Re: today's git commits noise

2016-12-05 12:06 GMT+01:00 Jonathan Gallimore : > No issue with the "noise", but thanks for heads up. > > One question - did we *delete* history? There's certainly commits I did > after September 16th but before December 4th which are no-where to be seen > here. I didn't even know you could do th

Re: today's git commits noise

No issue with the "noise", but thanks for heads up. One question - did we *delete* history? There's certainly commits I did after September 16th but before December 4th which are no-where to be seen here. I didn't even know you could do that. Irrespective of whatever issues there are with what I c