On 5/8/15 12:51 PM, Timo wrote:
> Hello everyone,
>
> I just noticed that the release notes for 3.4 [1] are a 404. Can
> someone with access take a look, please?
Thanks for pointing this out. As a workaround until we get the
content restored on the site, you can get the release notes from the
tag
On Fri, May 8, 2015 at 9:02 AM, Luc Maisonobe wrote:
> Le 08/05/2015 17:55, Adrian Crum a écrit :
> > Do the Git repos include the Subversion commit history?
>
> Yes, it includes the full history, including tags.
>
Seems reasonable to drop then.
Gary
>
> Luc
>
> >
> > Adrian Crum
> > Sandglas
Hello everyone,
I just noticed that the release notes for 3.4 [1] are a 404. Can
someone with access take a look, please?
Thanks
Timo
[1]
http://commons.apache.org/proper/commons-lang/release-notes/RELEASE-NOTES-3.4.txt
-
To u
The git owner is shown as
owner ARRAY(0x2b87708)
https://git-wip-us.apache.org/repos/asf?p=commons-lang.git;a=summary
This looks odd.
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
Le 08/05/2015 17:55, Adrian Crum a écrit :
> Do the Git repos include the Subversion commit history?
Yes, it includes the full history, including tags.
Luc
>
> Adrian Crum
> Sandglass Software
> www.sandglass-software.com
>
> On 5/8/2015 8:53 AM, sebb wrote:
>> Is there any point in keeping th
Do the Git repos include the Subversion commit history?
Adrian Crum
Sandglass Software
www.sandglass-software.com
On 5/8/2015 8:53 AM, sebb wrote:
Is there any point in keeping the SVN repos for components that have
moved to Git?
They are read-only (or should be) and are not synchronised with
Is there any point in keeping the SVN repos for components that have
moved to Git?
They are read-only (or should be) and are not synchronised with the
Git repo, so they can be confusing.
If there is a need to keep them, they should be renamed so people
cannot accidentally use them.
It might be a
