You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by sebb <se...@gmail.com> on 2009/04/18 18:16:39 UTC

Identifying the initial import in SVN

Is there a standard way to identify the initial import of a codebase in SVN?

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org


Re: Identifying the initial import in SVN

Posted by Craig L Russell <Cr...@Sun.COM>.
On Apr 18, 2009, at 9:16 AM, sebb wrote:

> Is there a standard way to identify the initial import of a codebase  
> in SVN?

No, there's a suggestion at http://incubator.apache.org/guides/mentor.html 
  to create a separate part of the repository to import the code base:

...Particular care needs to be taken with commit messages during clean  
up. The intended audience needs to include lawyers and code auditors.  
Members of the public need to be able to follow and understand the  
process from these messages alone.
It is therefore recommended that the initial source is (after being  
expanded from the archive) checked in as is into a special directory ($ 
{project}/trunk/import is suggested). The original packaging,  
copyright statements and license notices should be preserved.

Some podlings do: http://svn.apache.org/repos/asf/incubator/jsecurity/import/

But most podlings don't. So the only way I know of to identify the  
initial code base is to look through svn history.

Craig

>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>

Craig L Russell
Architect, Sun Java Enterprise System http://db.apache.org/jdo
408 276-5638 mailto:Craig.Russell@sun.com
P.S. A good JDO? O, Gasp!