On Sun, Feb 19, 2012 at 8:07 PM, John Leonard wrote:
> first, commit each one then update each one?
>>>
>>>
>>> Yes, normally these events are not strictly synchronized. Commit when
>> you
>> are sure a set of changes are in a state you want to save, and update when
>> you are ready to pick up
On Sun, 19 Feb 2012 20:12:31 -0500, Les Mikesell
wrote:
On Sun, Feb 19, 2012 at 6:34 PM, John Leonard
wrote:
What is a good way to keep multiple checkouts up to date? Would it be to
first, commit each one then update each one?
Yes, normally these events are not strictly synchronized.
On Sun, Feb 19, 2012 at 6:34 PM, John Leonard wrote:
> What is a good way to keep multiple checkouts up to date? Would it be to
> first, commit each one then update each one?
>
>
Yes, normally these events are not strictly synchronized. Commit when you
are sure a set of changes are in a state y
What is a good way to keep multiple checkouts up to date? Would it be to
first, commit each one then update each one?
John L.
--
Using Opera's revolutionary email client: http://www.opera.com/mail/
On 02/15/2012 11:05 AM, Philip Martin wrote:
Stefan Sperling writes:
But rather than going through that effort, I would recommend using
svnadmin dump/load, or svnsync with file:// URLs, until Subversion 1.8
is released. At which point you can switch over to using
"svnadmin hotcopy --incrementa
> From: leojhartiv [mailto:leo.h...@gmail.com]
> Sent: Saturday, February 18, 2012 8:36 AM
> To: users@subversion.apache.org
> Subject: Branching/Merging Strategy
>
> I wanted to describe our branching and merging strategy and hopefully get
> some feedback. We are using Subversion Server 1.6.
>
All true, but it would still have been nice for André's use case to
work. 'svn log' needs almost zero information from the wc, after all...
Stefan Sperling wrote on Sun, Feb 19, 2012 at 13:32:46 +0100:
> On Sun, Feb 19, 2012 at 03:25:52AM +0100, André Hänsel wrote:
> > Hi list,
> >
> > recently
OK, now I understand
Need to run #get-location-segments.py /repo/path/to/filename
And then it says example if the file foo has 3 other instances in history that
were replaced (R)
So get-location-segments.py works per file and not per repo, right?
Regards,
Ilya Rokhkin
Configuration Management Eng
On Sun, Feb 19, 2012 at 12:44:55PM +, Rokhkin, IlyaX wrote:
> Yes, it helps
> But the issue more complicated
> We have hundred such files in the repo, and we do not know the names, we want
> to find all those files that were replaced (R)
Well, if you run 'svn log' on the repository root it wi
Yes, it helps
But the issue more complicated
We have hundred such files in the repo, and we do not know the names, we want
to find all those files that were replaced (R)
In collabnet they said me that get-location-segments.py can find all such files
in the repo
Regards,
Ilya Rokhkin
Configuratio
On Sun, Feb 19, 2012 at 08:37:24AM +, Rokhkin, IlyaX wrote:
> Hi Stefan,
>
> Files were replaced (R) by merge, because they have 2 different ID, so one
> file with its history is deleted
> The idea is to find those deleted file with history
If I replace a file called 'alpha' and commit the r
On Sun, Feb 19, 2012 at 03:25:52AM +0100, André Hänsel wrote:
> Hi list,
>
> recently I noticed that I cannot view the log while an update of a working
> copy is running. It's quite annoying. I wonder if it has always been this
> way or if this is new in 1.7.
This is new in 1.7. It happens becaus
Hi Stefan,
Files were replaced (R) by merge, because they have 2 different ID, so one file
with its history is deleted
The idea is to find those deleted file with history
Regards,
Ilya Rokhkin
Configuration Management Engineer
Intel - Data, storage and SW Team
iNET: 8-920-6165
Tel: +972-3-929616
13 matches
Mail list logo
