David,
Ok, thanks for settings the record straight. These nuances are important to me.
I definitely like the passion you guys have, the big plans, and the
intention to take the bull by the horns :-). I hope you can get the
ball rolling, with an actively participating community, and make
Afternoon,
For some client-side Tortoise hooks (which are for the purpose of
preventing people shoot themselves in the head in all the myriad ways
Subversion allows), I need to get the ancestor-branch, ie where the
current branch/tag was copied from.
My current strategy for doing this is svn log
That would be a more efficient way to a achieve it but as you say that might
not work in all cases.
In my opinion a feature like that is enough important to be provided by
Subversion via cmd line / API, because that is the one of the bridges
between Subversion and Change Management tools (like
hi,
My former team member had put some code in a public repository
sometime back.Currently I am the sole team member now and need to
modify the code.
I am relatively new to subversion and version control systems in
general..
I can checkout the code using
svn checkout
My former team member had put some code in a public repository
sometime back.Currently I am the sole team member now and need to
modify the code.
I am relatively new to subversion and version control systems in
general..
I can checkout the code using
svn checkout
On Wednesday 22 December 2010, mark jason wrote:
I am relatively new to subversion and version control systems in
general..
Read the introduction in the book (see my signature). Set up a toy repository
for testing things. You can even clone the life repository if you want to
check how things
Guten Tag mark jason,
am Mittwoch, 22. Dezember 2010 um 14:42 schrieben Sie:
How should I go about this?
First of all you should read at a least a bit through the docs and get
to know about best practices, what is possible etc.
http://svnbook.red-bean.com/nightly/en/svn-book.html
should I
If you have concrete suggestions for improving or extending the core,
we'll welcome them --- on the dev@ list please.
Pablo Beltran wrote on Wed, Dec 22, 2010 at 14:26:13 +0100:
That would be a more efficient way to a achieve it but as you say that might
not work in all cases.
In my opinion
Echlin, Jamie wrote on Wed, Dec 22, 2010 at 13:09:24 -:
Afternoon,
For some client-side Tortoise hooks (which are for the purpose of
preventing people shoot themselves in the head in all the myriad ways
Subversion allows), I need to get the ancestor-branch, ie where the
current
For some client-side Tortoise hooks (which are for the purpose of
preventing people shoot themselves in the head in all the myriad ways
Subversion allows), I need to get the ancestor-branch, ie where the current
branch/tag was copied from.
When I create a new branch I add an svn:property,
You're welcome and I *really* appreciated the opportunity to set the
record straight. Whenever you put your head above the parapet...
On Wed, Dec 22, 2010 at 1:54 AM, Johan Corveleyn jcor...@gmail.com wrote:
David,
Ok, thanks for settings the record straight. These nuances are important to
Chris Tashjian wrote on Wed, Dec 22, 2010 at 11:34:03 -0500:
For some client-side Tortoise hooks (which are for the purpose of
preventing people shoot themselves in the head in all the myriad ways
Subversion allows), I need to get the ancestor-branch, ie where the current
branch/tag was
On Wed, Dec 22, 2010 at 09:12:13AM +0800, David Xie wrote:
Thanks Stefan.
Wow, it really works when disable authz. This means I could access to svn://
172.18.127.148/test (read and write) and successfully to view log
history. Hard to believe!
#authz-db = authz
And the logs are showed
On Wed, Dec 22, 2010 at 01:09:24PM -, Echlin, Jamie wrote:
Afternoon,
For some client-side Tortoise hooks (which are for the purpose of
preventing people shoot themselves in the head in all the myriad ways
Subversion allows), I need to get the ancestor-branch, ie where the
current
I'm happy to announce the release of Subversion 1.5.9. This release
is intended for users who are still running the 1.5 release line, and
contains a number of stability and performance fixes to previous 1.5.x
releases. This release does *not* contain all the bug fixes and
features which are
15 matches
Mail list logo
