Re: [ jEdit-users ] Committing all changed files

[Dale A. <da...@gr...>]

Best practice is to do a 'status' on the project, then commit from the
status results. It is good practice to commit files that logically go
together, it makes reverting (if necessary) much easier and makes it
easier for others to see which revision fixed what problem. There are
other advantages:

- if you do the status against the repository, it will tell you if you
have files that are out of date and need to be updated/merged before
committing.
- the status results will alert you to files that need to be added
before committing
- it is easier to select and commit files that go together in logical groups
- is is easier to notice files that you changed but should be reverted
rather than committed.

I haven't used Tortoise in years, so I don't know how it handles
committing an entire project/directory. Does it do these things for
you?

Dale



On Mon, Jan 31, 2011 at 6:53 AM, Mordechai Ben-Ari
<Mot...@we...> wrote:
> The problems I had last week with SVN and PV seem
> to have resolved themselves by reinstalling and
> recreating the project.
>
> One question: in Tortoise SVN, I can commit
> the project directory and it will automatically select
> all changed files for the commit operation.
> This doesn't work with PV; it seems that I have to select
> each changed file individually.
> Am I missing something?
>
> Thanks
> Moti
>
>
>
> ------------------------------------------------------------------------------
> Special Offer-- Download ArcSight Logger for FREE (a $49 USD value)!
> Finally, a world-class log management solution at an even better price-free!
> Download using promo code Free_Logger_4_Dev2Dev. Offer expires
> February 28th, so secure your free ArcSight Logger TODAY!
> http://p.sf.net/sfu/arcsight-sfd2d
> --
> -----------------------------------------------
> jEdit Users' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-users
>