You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Arthur Chan <ar...@gmail.com> on 2010/03/20 16:53:42 UTC
SVN respository expiry date
Dear Sir or Madam,
I am writing to request your help for authority information about SVN
logging and commit information.
I am requesting SVN checkin time from my previous company. I have worked
there for 2 years and left the company in Aug 2009.
However, they told me that SVN only store logs for 3 months by default so
that all my commit time were lost.
Could I ask whether SVN has a 3 months respository expiry limit? And how can
retrieved check-in time of all my commit in SVN?
I appreciate your help very much!
Best Regards,
Arthur
Re: SVN respository expiry date
Posted by Ulrich Eckhardt <ec...@satorlaser.com>.
On Saturday 20 March 2010, Arthur Chan wrote:
> I am writing to request your help for authority information about SVN
> logging and commit information.
>
> I am requesting SVN checkin time from my previous company. I have worked
> there for 2 years and left the company in Aug 2009.
>
> However, they told me that SVN only store logs for 3 months by default so
> that all my commit time were lost.
They are either incompetent or lying.
> Could I ask whether SVN has a 3 months respository expiry limit? And how
> can retrieved check-in time of all my commit in SVN?
One of the design principles of Subversion was to never(!) throw away any
data. Only as an admin with file-level access to a repository you could
delete parts of the history and even that requires explicit interaction.
Just wondering, but why do you care? Or why do they care?
Uli
--
ML: http://subversion.tigris.org/mailing-list-guidelines.html
FAQ: http://subversion.tigris.org/faq.html
Docs: http://svnbook.red-bean.com/
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Sator Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at <http://www.satorlaser.de/>
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Sator Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
Re: SVN respository expiry date
Posted by Arthur Chan <ar...@gmail.com>.
Hi Jon,
Thanks a bunch, your information is very useful for me!
Best,
Arthur
On Mon, Mar 22, 2010 at 8:37 PM, Jon Foster <Jo...@cabot.co.uk> wrote:
> Hi,
>
> Arthur Chan wrote:
> > I am requesting SVN checkin time from my previous company.
> ...
> > However, they told me that SVN only store logs for 3 months
> > by default so that all my commit time were lost.
>
> There are 2 different places you can get "commit time" information.
>
> First, there are the logs from Subversion. These are reliable
> (no-one apart from the system administrator could forge them). They
> are optional - you don't have to generate them. If you do generate
> them, then it's up to you to decide how long to store them for. They
> can log all activity, including commits, checkouts, and updates.
>
> I suspect the logs are what your company is talking about, and it's
> quite plausible for them to be stored for only 3 months.
>
> Secondly, there is the "svn:date" revision property in the
> repository. These may or may not be reliable, depending on whether
> your repository has a "pre-revprop-change" hook that allows them to
> be changed. (By default, they cannot be forged by anyone other than
> the system administrator. But if your system administrator
> installs a "pre-revprop-change" hook that allows it, then any
> committer can change them to any value, without leaving an audit
> trail). They are generated automatically by Subversion, you can't
> (easily) turn them off. Subversion will store them forever (or
> until someone changes or deletes them). These only tell you the
> commit time, they won't tell you about checkouts or updates.
>
> Kind regards,
>
> Jon
>
> --
> (Please direct all replies to the mailing list)
>
>
> **********************************************************************
> This email and its attachments may be confidential and are intended solely
> for the use of the individual to whom it is addressed. Any views or opinions
> expressed are solely those of the author and do not necessarily represent
> those of Cabot Communications Ltd.
>
> If you are not the intended recipient of this email and its attachments,
> you must take no action based upon them, nor must you copy or show them to
> anyone.
>
> Cabot Communications Limited
> Verona House, Filwood Road, Bristol BS16 3RY, UK
> +44 (0) 1179584232
>
> Co. Registered in England number 02817269
>
> Please contact the sender if you believe you have received this email in
> error.
>
> **********************************************************************
>
>
> ______________________________________________________________________
> This email has been scanned by the MessageLabs Email Security System.
> For more information please visit http://www.messagelabs.com/email
> ______________________________________________________________________
>
RE: SVN respository expiry date
Posted by Jon Foster <Jo...@cabot.co.uk>.
Hi,
Arthur Chan wrote:
> I am requesting SVN checkin time from my previous company.
...
> However, they told me that SVN only store logs for 3 months
> by default so that all my commit time were lost.
There are 2 different places you can get "commit time" information.
First, there are the logs from Subversion. These are reliable
(no-one apart from the system administrator could forge them). They
are optional - you don't have to generate them. If you do generate
them, then it's up to you to decide how long to store them for. They
can log all activity, including commits, checkouts, and updates.
I suspect the logs are what your company is talking about, and it's
quite plausible for them to be stored for only 3 months.
Secondly, there is the "svn:date" revision property in the
repository. These may or may not be reliable, depending on whether
your repository has a "pre-revprop-change" hook that allows them to
be changed. (By default, they cannot be forged by anyone other than
the system administrator. But if your system administrator
installs a "pre-revprop-change" hook that allows it, then any
committer can change them to any value, without leaving an audit
trail). They are generated automatically by Subversion, you can't
(easily) turn them off. Subversion will store them forever (or
until someone changes or deletes them). These only tell you the
commit time, they won't tell you about checkouts or updates.
Kind regards,
Jon
--
(Please direct all replies to the mailing list)
**********************************************************************
This email and its attachments may be confidential and are intended solely for the use of the individual to whom it is addressed. Any views or opinions expressed are solely those of the author and do not necessarily represent those of Cabot Communications Ltd.
If you are not the intended recipient of this email and its attachments, you must take no action based upon them, nor must you copy or show them to anyone.
Cabot Communications Limited
Verona House, Filwood Road, Bristol BS16 3RY, UK
+44 (0) 1179584232
Co. Registered in England number 02817269
Please contact the sender if you believe you have received this email in error.
**********************************************************************
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________