[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [Subclipse-users] Subclipse Export

From: Shelley <randomshelley_at_gmail.com>
Date: 2007-11-06 00:29:00 CET

In the use case I described, the students will use the projects once. There
won't be a need for any svn actions after initial checkout (no need for
updates, commits, switches, logs, etc).

The priority of such an enhancement is low as it relates to my particular
use case (a checkout will suffice), but there still is a desire for this
behavior.

Thanks for your responses.

On 11/5/07, Mark Phippard <markphip@gmail.com> wrote:
>
> On 11/5/07, Shelley <randomshelley@gmail.com> wrote:
> > When sharing common projects, there is not always a need for all users
> to
> > always have the svn metadata when they will not be committing any
> changes.
> > Exporting the entire parent directory and then importing the individual
> > projects into Eclipse is not a desirable workflow.
> >
> > For one current, specific use case, I have several projects checked into
> > source control which are used as lab projects in a course I am
> developing.
> > Whether or not permissions are restricted in source control (in this
> case
> > they are), there is no need for the students to have the svn metadata.
> > Project checkouts would not be detrimental in this case, but exporting
> the
> > projects would be preferred.
>
> You can file an issue but I do not see us doing this. The metadata is
> not just needed for commits, it is also needed for update/switch etc.
> If they need the code once, why would they not need a future version?
>
> --
> Thanks
>
> Mark Phippard
> http://markphip.blogspot.com/
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
Received on Tue Nov 6 00:29:11 2007

This is an archived mail posted to the Subclipse Users mailing list.