Please use your email program's Reply All feature so your replies go to the
list too, not just to me.
On Feb 24, 2010, at 23:27, Julio alarcon wrote:
> On Wed, Feb 24, 2010 at 11:11 PM, Ryan Schmidt wrote:
>
>> Let's keep this discussion on the mailing list so all can benefit from what
>> we l
Let's keep this discussion on the mailing list so all can benefit from what we
learn.
On Feb 24, 2010, at 22:31, Julio alarcon wrote:
> On Wed, Feb 24, 2010 at 9:04 PM, Ryan Schmidt wrote:
>
>> On Feb 24, 2010, at 20:01, Julio alarcon wrote:
>>
>>> Hi i was trying to do some osx cloning but i
On Feb 24, 2010, at 20:01, Julio alarcon wrote:
> Hi i was trying to do some osx cloning but i figured it out that i needed
> subversion, but there is no one for pcbsd but it is for freebsd and i don't
> really know how to make it work in pcbsd, ill be glad if i can find some help
> or a subve
Hi i was trying to do some osx cloning but i figured it out that i needed
subversion, but there is no one for pcbsd but it is for freebsd and i don't
really know how to make it work in pcbsd, ill be glad if i can find some
help or a subversion for pcbsd thx.
On Feb 24, 2010, at 15:23, Mark Branson wrote:
> trying to change a file extension from ".f90" to ".F90". tried using quotes
> but that fails, too. what am i missing?
This is a FAQ:
http://subversion.apache.org/faq.html#case-change
Subversion cannot rename an item when you change only its case unless
the underlying filesystem is case sensitive. OSX and Windows
filesystems are case-preserving but not case-sensitive. You should be
able to rename this item directly in the repository and then run svn
update. Or rename it on Li
trying to change a file extension from ".f90" to ".F90". tried using quotes
but that fails, too. what am i missing?
/Users/mark/mmf/SPCAM/trunk/models/atm/cam/src/physics/crm> svn move
abcoefs.f90 abcoefs.F90
svn: Path 'abcoefs.F90' is not a directory
/Users/mark/mmf/SPCAM/trunk/models/atm/ca
Hello,
I have looked for ways to migrate old repositories to latest 1.6.x.
And I let the "dump/import" apart because my window maintenance was too short
and my available disk space too limit to migrate my company's 200 repositories,
around 27 Gb.
So in a first step, I have just apply "svnadmin
I suspect that the external isn't updated automatically for the committer in
this case is it?
I haven't used externals, but I'm willing to bet a fair amount of money
on it. The committer doesn't update any versioned files - neither those
being committed, because they _are_ the new version, no
> -Original Message-
> From: Stein Somers [mailto:ssom...@opnet.com]
> Sent: 24 February 2010 13:50
> To: users@subversion.apache.org
> Subject: Re: Modify files in start-commit
>
> On second thought, how about this: don't change the transaction, but
> keep the VERSION file in a separa
On second thought, how about this: don't change the transaction, but
keep the VERSION file in a separate repository, that you reference
through svn:external. That way, you don't modify the contents of the
transaction - you just add a second transaction. Of course it's your
responsibility to tie
Hi
Not sure I really understand the problem, but how about creating a
tag(version) in post-commit?
/component/trunk -> /component/version/build
Cheers / Erik
On Wed, Feb 24, 2010 at 12:34 PM, Bailey, Darragh wrote:
>
> Is it possible to modify files in a start-commit hook and include them wit
On 24/02/2010 12:34, Bailey, Darragh wrote:
Is it possible to modify files in a start-commit hook and include them with a
commit?
As far as I know, you can't even tell which files are modified in the
start-commit hook.
You can tell in the pre-commit hook, but its template shouts
# *** N
I have subversion 1.6.9 server and 1.6.7 client. I do a merge from
branch to trunk
My working copy is up-to-date. If I do a merge, I end up with a warning
"tree conflicts", but if I resolve the conflict, its says Working copy
is out of date, so I have to do a update and then commit
May I know,
Is it possible to modify files in a start-commit hook and include them with a
commit?
We have multiple components here in the same svn tree, and we'd like to bump a
release number on each one as commits occur. Rather than trying to add code to
check how many commits have been made to the area
On Wed, 17 Feb 2010, dcz wrote:
> Here is what I'm trying to do : some user (let's call them junior
> developer) should require their commit to be authorized by other
> (senior developer) before they would actually be committed.
You could require the junior developer to put a line like this
in the
Le 22/02/2010 06:58, Srilakshmanan, Lakshman a écrit :
Hi Dcz,
One point of clarification. Each JD does ** not ** have their own branch.
Each ** change ** has a branch. If the change is large and more than one
developer is working on the change, they will all work in the same branch.
Hello S
17 matches
Mail list logo
