2011/5/12 Dave Tingling :
> Thanks for those tips Konstantin.
>
> There are about 16 developers. Is there anything I can look at on the server
> side to determine whether such bad directory copy/moves have been done, and
> perhaps by whom?
>
When developer B notices "Frankenstein" file appearing i
> Hi Bob,
> > Does the same team us more than one repository? Or is each repo
> used by different people and teams?
> >
> >
> Some members of this team do work with other repositories. But this
> small team (7-10 active devs) is the only one that touches this
> problematic repository.
This makes
Hi Bob,
Does the same team us more than one repository? Or is each repo used by
different people and teams?
Some members of this team do work with other repositories. But this
small team (7-10 active devs) is the only one that touches this
problematic repository.
Is the update funky whe
Guten Tag Dave Tingling,
am Donnerstag, 12. Mai 2011 um 16:26 schrieben Sie:
> We will. Let me make sure I understand you: you're suggesting testing
> multiple commits, but each consecutive commit will be an "undoing" of
> the previous change. If that's true, after many many commits, I have
>
Thorsten Schöning wrote:
I would try to test a bit: Take a dev where the file never was freaky
and let him produce small changes which are committable, e.g. add a
newline at the end of the file and remove it or stuff like that. But
it should be always the same changes.
We will. Let me make sure I
> Thanks for those tips Konstantin.
>
> There are about 16 developers. Is there anything I can look at on
> the
> server side to determine whether such bad directory copy/moves have
> been
> done, and perhaps by whom?
>
> > On the server: what protocol you are using to access the
> repository and
Thanks for those tips Konstantin.
There are about 16 developers. Is there anything I can look at on the
server side to determine whether such bad directory copy/moves have been
done, and perhaps by whom?
On the server: what protocol you are using to access the repository and
commit the files
Hi, Les,
> Von: Les Mikesell [mailto:lesmikes...@gmail.com]
> Remember that a more typical use of externals is to include components
> that have their own separate release schedules.
Yes, in that light, it makes acutally sense to exclude externals from
the commit by default, so the user has to e
On 5/12/11 1:39 AM, Markus Schaber wrote:
I can commit files and directories from inside and outside the
external directory in the same commit, as long as the external
directory itself is not mentioned on the list of elements to commit.
I'd consider that accidental and not count on it.
Acci
Guten Tag Dave Tingling,
am Mittwoch, 11. Mai 2011 um 21:40 schrieben Sie:
>> When someone experiences the error, Their local copy will show as
>> modified immediately after the update, and attempting to commit the
>> working copy directory will include these changes. No conflict will be
>> dete
10 matches
Mail list logo
