Original WC revision

[Toby Johnson <to...@etjohnson.us>]

Is there a way to tell the original revision a working copy was at when 
it was first checked out, even after it has undergone updates?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

mailer.py and mailer.conf.example inconsistent about generate_diffs

[Ken Johnson <KJ...@eclypse.org>]

Hello,

I grabbed a copy of mailer.py and mailer.conf.example from the repository
in order to be able to use the helpful ViewCVS patch which supplies
ViewCVS difference URLs in commit emails.  In our environment, I need to
suppress the difference listings in the email, and discovered
that "generate_diffs = " still provides diffs (inconsistent
with description in mailer.conf).  However, "generate_diffs = FOO" 
suppresses diffs, just as described.  This situation looks like
it might be the result of trying to provide backward compatibility
with "suppress_adds" and "suppress_deletes".

Re: Original WC revision

[Toby Johnson <to...@etjohnson.us>]

Toby Johnson wrote:

> Actually, though, it's not so often that the WC is actually updated.. 
> so in that case, is there a way to accomplish this, even if all files 
> in the WC have been commited (or are new adds)? 

Hmmm, I seem to have completely overlooked the "svnversion" tool. This 
is exactly what I need. You guys think of everything! :)

Out of curiosity, why is this a separate tool? (And no, I dare not 
suggest that "svn version" should replace this!!)

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Original WC revision

[Toby Johnson <to...@etjohnson.us>]

Max Bowsher wrote:

>Toby Johnson wrote:
>  
>
>>Rather than branching for each task/ticket, we create a new working copy
>>of a particular portion of the repository for each ticket. Sometimes
>>that WC is committed/updated multiple times (for big tasks, our managers
>>prefer commiting often, rather than just once when the ticket is
>>finished), and I was wondering if there's a way to, in a particular
>>working copy, automatically diff between HEAD and when that WC was first
>>created.
>>
>>But as long as people put the ticket # at the beginning of their log
>>message, it's not that big a deal.
>>    
>>
>
>Hmm. Doesn't provide any isolation from what other developers are doing.
>Though it does isolate multiple different changes being worked on by the
>same developer simultaneously.
>
Hey man, you're preaching to the choir. I have to fight my battles one 
at a time. :)

The problem is that for some reason there are developers on my team who 
are very prone to wiping out weeks' worth of work, and getting a backup 
from tape takes at least a day, which is usually about 23 hours too 
late. So version control has the added function of ad-hoc backups for us.

Actually, though, it's not so often that the WC is actually updated.. so 
in that case, is there a way to accomplish this, even if all files in 
the WC have been commited (or are new adds)?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Original WC revision

[Max Bowsher <ma...@ukf.net>]

Toby Johnson wrote:
> Max Bowsher wrote:
>
>> Toby Johnson wrote:
>>
>>
>>> Is there a way to tell the original revision a working copy was at when
>>> it was first checked out, even after it has undergone updates?
>>>
>>>
>>
>> No. Why?
>>
>>
> Rather than branching for each task/ticket, we create a new working copy
> of a particular portion of the repository for each ticket. Sometimes
> that WC is committed/updated multiple times (for big tasks, our managers
> prefer commiting often, rather than just once when the ticket is
> finished), and I was wondering if there's a way to, in a particular
> working copy, automatically diff between HEAD and when that WC was first
> created.
>
> But as long as people put the ticket # at the beginning of their log
> message, it's not that big a deal.

Hmm. Doesn't provide any isolation from what other developers are doing.
Though it does isolate multiple different changes being worked on by the
same developer simultaneously.

Once a WC has had all local mods committed or reverted, and all extra and
ignored files erased, and been updated, it's exactly equivalent to a fresh
checkout, and there is no need to discard it and pull down all that data
from the server again.

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Original WC revision

[Toby Johnson <to...@etjohnson.us>]

Max Bowsher wrote:

>Toby Johnson wrote:
>  
>
>>Is there a way to tell the original revision a working copy was at when
>>it was first checked out, even after it has undergone updates?
>>    
>>
>
>No. Why?
>  
>
Rather than branching for each task/ticket, we create a new working copy 
of a particular portion of the repository for each ticket. Sometimes 
that WC is committed/updated multiple times (for big tasks, our managers 
prefer commiting often, rather than just once when the ticket is 
finished), and I was wondering if there's a way to, in a particular 
working copy, automatically diff between HEAD and when that WC was first 
created.

But as long as people put the ticket # at the beginning of their log 
message, it's not that big a deal.

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org

Re: Original WC revision

[Max Bowsher <ma...@ukf.net>]

Toby Johnson wrote:
> Is there a way to tell the original revision a working copy was at when
> it was first checked out, even after it has undergone updates?

No. Why?

Max.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org