As far as I can tell this only affected 2 commits. I have reapplied
them both. But please double check any work you did for 4.0.1
On Fri 13 Jan 2012 10:34:27 AM CST, Steve Ebersole wrote:
> We have a "best effort" solution to find stuff that gotten
> over-written. The premise is that reflog sh
We have a "best effort" solution to find stuff that gotten
over-written. The premise is that reflog shows these commits, while
they no longer show up in log. Thats true unless git locally ran a gc
on your repo.
Anyway, the idea of the best effort is to compare reflog against log
for all jira
Well however it happened at least some commits are missing.
It happened between 4.0 and 4.0.1. So like Sanne said it is best if
everyone checks any work they committed to make sure it is still there.
The only way this happens is if someone did a forced push. We have
talked about this before.
4.1. Not even sure there will be a 4.0.2
On Fri 13 Jan 2012 07:32:09 AM CST, Gail Badner wrote:
> In case you missed my message...
>
> I've kept http://docs.jboss.org/hibernate/core/ as is with 4.0.1.Final
> documentation and:
> - added a symbolic link for http://docs.jboss.org/hibernate/orm/ th
In case you missed my message...
I've kept http://docs.jboss.org/hibernate/core/ as is with 4.0.1.Final
documentation and:
- added a symbolic link for http://docs.jboss.org/hibernate/orm/ that points to
http://docs.jboss.org/hibernate/core/
- updated the symbolic link for http://docs.jboss.org/h
On 01/13/2012 01:58 AM, Hardy Ferentschik wrote:
>>
>> I agree, we should do a redirect. I had not planned on changing the
>> physical dir until 4.1 as that is when the new docs would be getting used.
>> 6 in one... if you feel the itch, go for it.
>
> Changing the directory name is easy. For
Interesting. I was trying `git log --grep=HHH-6906` but getting nothing
back.
`git reflog | grep HHH-6906` returns:
39d47c4 HEAD@{89}: commit: HHH-6906 - Clean up javadoc warnings
I only use my fork for "on going" work, especially if it has to be
collaborated. I never used my fork for this wo
I've kept http://docs.jboss.org/hibernate/core/ as is with 4.0.1.Final
documentation and:
- added a symbolic link for http://docs.jboss.org/hibernate/orm/ that points to
http://docs.jboss.org/hibernate/core/
- updated the symbolic link for http://docs.jboss.org/hibernate/stable/core/ to
point t
I've checked the repos as well and came to same conclusions as Scott,
which is we need to recover the patch from Steve's local repository;
but also I'd recommend to check for all changes as tracked in JIRA
around the suspected timeframe and verify if they are in practice
included in the current mas
>>> I also noticed that the Javadoc includes test classes. It would be nice to
>>> exclude those.
>>
>> right, even the aggregated docs seem to include test classes. I would create
>> a jira and we reconfigure the task for the next release
>
> Hmm, I spent a lot of time getting those right.
>
On Jan 12, 2012, at 9:20 PM, Scott Marlow wrote:
> Do you know which JAR needs to see the extensions? I need to make sure that
> they become visible to whichever jar needs to see them.
The extensions are loaded by the Infinispan Core jar, so that's the one I'd
assume needs to see the Hibernat
11 matches
Mail list logo
