I would like to be able to create a tag using the SVN copy command so
that the timestamps on the files in the destination are the same as
those in the source.
Is this possible?
Is there an easy way to restrict svn diff operation to files of a
certain extension (say .h)? A quick glance at the manual suggested
nothing to me.
On 03/24/2011 05:11 PM, Bob Archer wrote:
On 03/24/2011 05:01 PM, Bob Archer wrote:
On 03/23/2011 08:02 PM, David Huang wrote:
On Mar 23, 2011, at 7:52 PM, Pat Farrell wrote:
On 03/23/2011 08:34 PM, Konstantin Kolinko wrote:
You are not giving much specifics, so how can people know
what
On 03/24/2011 05:01 PM, Bob Archer wrote:
On 03/23/2011 08:02 PM, David Huang wrote:
On Mar 23, 2011, at 7:52 PM, Pat Farrell wrote:
On 03/23/2011 08:34 PM, Konstantin Kolinko wrote:
You are not giving much specifics, so how can people know what
is going on
in your case?
Specifics for c
On 03/23/2011 08:09 PM, Pat Farrell wrote:
On 03/23/2011 09:02 PM, David Huang wrote:
If you're sure that the mergeinfo is bogus, why not just delete it?
e.g., svn propdel svn:mergeinfo
fnfapp/src/java/com/fnfbook/bean/FilterListBase.java
I'm sure. I'll try that.
I have not tried it before,
On 03/23/2011 08:02 PM, David Huang wrote:
On Mar 23, 2011, at 7:52 PM, Pat Farrell wrote:
On 03/23/2011 08:34 PM, Konstantin Kolinko wrote:
You are not giving much specifics, so how can people know what is going on
in your case?
Specifics for complete 100% reproducable problem:
do svn up
On 03/23/2011 05:36 PM, Pat Farrell wrote:
Since then, these files are picked up for properties merges whenever I merge
their project even though they haven't really changed in years. How can I
FIX this merge info so I stop being bothered by them.
Wouldn't "svn revert filename" clear this? Or d
Somewhere back in the distant past, I was a bad bad boy and did
something that SVN didn't like to get some merge to work. This happened
about two years ago.
Since then, these files are picked up for properties merges whenever I
merge their project even though they haven't really changed in ye
I work with a very senior colleague who has never always resisted
version control and would much rather do without it, but he is forced to
go along and I am the whipping boy whenever something goes wrong.
He poses a general but simple question that I find myself unable to give
a simple answer
I work with a very senior colleague who has never always resisted
version control and would much rather do without it, but he is forced to
go along and I am the whipping boy whenever something goes wrong.
He poses a general but simple question that I find myself unable to give
a simple answer
On 01/20/2011 05:19 AM, Stephen Butler wrote:
A 'C' in the third column indicates a tree conflict, while a 'C' in
Thanks, Stephen.
While we're on the subject, can you tell me succinctly what is the exact
definition of a "tree conflict"? This used to drive me nuts when I used
the subclip
On 01/20/2011 04:28 AM, JamieEchlin wrote:
Stephen Butler wrote:
On the command line, try
svn help update
(for instance).
It's also in the SVN Book's command reference chapter, under
the given 'svn' subcommand:
There is docn for the letters for status and for update, but I haven't f
Where is this documented? I sometimes see letters I don't know, such as
"G", what is that for - and these outputs may differ from command to
command. Also the column in which a letter appears is significant.
Can someone please point me to a document where this is explained? It's
not in the
On 12/02/2010 10:23 AM, Steve Cohen wrote:
On 12/01/2010 12:29 PM, Steve Cohen wrote:
I have a need to define a number of svn:ignore patterns in my project.
Some are specific directories somewhere in my project tree. Others are
particular file types created by a build process such as *.o which
On 12/02/2010 05:24 PM, Bob Archer wrote:
On 12/02/2010 08:39 AM, Bob Archer wrote:
$ svn update
svn: Unable to lock 'utscmd'
$ svn propget svn:ignore
utspkg_src
utscmd
utslib
utsbin
utstool
utscmd is a subdirectory of the current working directory. It
is
included in svn:ignore. Why is svn
On 12/02/2010 08:39 AM, Bob Archer wrote:
$ svn update
svn: Unable to lock 'utscmd'
$ svn propget svn:ignore
utspkg_src
utscmd
utslib
utsbin
utstool
utscmd is a subdirectory of the current working directory. It is
included in svn:ignore. Why is svn even trying to lock this
directory?
The seq
On 12/01/2010 12:29 PM, Steve Cohen wrote:
I have a need to define a number of svn:ignore patterns in my project.
Some are specific directories somewhere in my project tree. Others are
particular file types created by a build process such as *.o which may
be found in any number of directories
:ignore). Is there any way of
achieving this? There doesn't appear to be one. Yet without it,
svn:ignore is useless, or at least too cumbersome to be used well.
Steve Cohen
Does svn propset svn:ignore accept the **/filename idiom as a legitimate
pattern indicating recursion or are you s
On 12/01/2010 03:33 PM, Ryan Schmidt wrote:
On Dec 1, 2010, at 15:19, Steve Cohen wrote:
It seems to me that
svn --recursive propset svn:ignore xyz
is basically just syntactic sugar for manually going through issuing
svn propset svn:ignore xyz
on every node of the directory
On 12/01/2010 02:08 PM, Ryan Schmidt wrote:
Redirecting this discussion back to the mailing list..
On Dec 1, 2010, at 14:05, Steve Cohen wrote:
On 12/01/2010 01:38 PM, Ryan Schmidt wrote:
Can you have the build process write its files to a different directory (a
"build" direc
The build process of the application I am bringing under svn creates a
number of unix binary executables that have no extension : for example
abcde
fghqp
etc.
I believe that * will match any files with or without periods so it
isn't suitable. Is there a pattern specifier that would embrace a
e one. Yet without it,
svn:ignore is useless, or at least too cumbersome to be used well.
Steve Cohen
s that the project was checked out and then
its build command run. The build command created a number of
directories, which have been added to svn:ignore so as not to figure in
svn at all.
What am I failing to understand here?
Steve Cohen
s that the project was checked out and then
its build command run. The build command created a number of
directories, which have been added to svn:ignore so as not to figure in
svn at all.
What am I failing to understand here?
Steve Cohen
24 matches
Mail list logo
