Workbench branching and tagging

Is there a way to do branching and tagging in workbench
other than the 
copy/cut and paste of the working copy?  The Workbench web
page states 
that it supports all client operations, but I cannot find a
way to get 
it to perform copy or move on a URL.  My repositories are
managed in the 
recommended way with /trunk, /tags, and /branches and me and
my users 
always just check out /trunk.  This cut and paste interface
is quite 
klunky as it won't let me put a different target name.  For
example, I 
want to copy my current /trunk to /tags/some-example-tag. 
Right now I 
have to do this copy and paste then rename /tags/trunk to be

/tags/some-example-tag.  All I wanted to do was tag my code
in the 
repository!!!

Thanks,
Larry

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribepysvn.tigris.org
For additional commands, e-mail: users-helppysvn.tigris.org

On Feb 4, 2007, at 01:52, Larry Schiefer wrote:

> Is there a way to do branching and tagging in workbench
other than  
> the copy/cut and paste of the working copy?

Not at the moment. This will require a repository browser
facility  
that is not written yet.

>   The Workbench web page states that it supports all
client  
> operations, but I cannot find a way to get it to
perform copy or  
> move on a URL.  My repositories are managed in the
recommended way  
> with /trunk, /tags, and /branches and me and my users
always just  
> check out /trunk.  This cut and paste interface is
quite klunky as  
> it won't let me put a different target name.  For
example, I want  
> to copy my current /trunk to /tags/some-example-tag. 
Right now I  
> have to do this copy and paste then rename /tags/trunk
to be /tags/ 
> some-example-tag.  All I wanted to do was tag my code
in the  
> repository!!!
>

The Cut and Paste is great for rearranging files in the
working copy but
as you say not suitable as a tag/branch creation method.

In work flow that I use a work and for open source projects
I do not  
tag or branch
that often. All my projects have a script that I run to tag
a release  
and create a branch
to save having to remember the long URLs and to check that
the tag/ 
branch does
not already exist.

Barry

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribepysvn.tigris.org
For additional commands, e-mail: users-helppysvn.tigris.org

Barry Scott wrote:
>
> On Feb 4, 2007, at 01:52, Larry Schiefer wrote:
>
>> Is there a way to do branching and tagging in
workbench other than 
>> the copy/cut and paste of the working copy?
>
> Not at the moment. This will require a repository
browser facility 
> that is not written yet.
>
What about the ability to copy to URL as a first step?  No
repo browser 
facility required (though it would ultimately be helpful.)

>>   The Workbench web page states that it supports
all client 
>> operations, but I cannot find a way to get it to
perform copy or move 
>> on a URL.  My repositories are managed in the
recommended way with 
>> /trunk, /tags, and /branches and me and my users
always just check 
>> out /trunk.  This cut and paste interface is quite
klunky as it won't 
>> let me put a different target name.  For example, I
want to copy my 
>> current /trunk to /tags/some-example-tag.  Right
now I have to do 
>> this copy and paste then rename /tags/trunk to be 
>> /tags/some-example-tag.  All I wanted to do was tag
my code in the 
>> repository!!!
>>
>
> The Cut and Paste is great for rearranging files in the
working copy but
> as you say not suitable as a tag/branch creation
method.
>
> In work flow that I use a work and for open source
projects I do not 
> tag or branch
> that often. All my projects have a script that I run to
tag a release 
> and create a branch
> to save having to remember the long URLs and to check
that the 
> tag/branch does
> not already exist.
>
Ok...but it would be nice if Workbench was a 1-stop shop for

everything.  The goal (at least for me and my co-workers)
when using a 
tool is to have it as the sole tool we use.  Requiring the
CLI to handle 
"normal" operations in a work flow like branching
and tagging can be a 
real pain.  Is it on the roadmap to allow copying to/from
URLs as 
supported in the CLI?

Thanks,
Larry

> Barry
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: users-unsubscribepysvn.tigris.org
> For additional commands, e-mail: users-helppysvn.tigris.org
>
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribepysvn.tigris.org
For additional commands, e-mail: users-helppysvn.tigris.org

On Feb 11, 2007, at 15:24, Larry Schiefer wrote:

> Barry Scott wrote:
>>
>> On Feb 4, 2007, at 01:52, Larry Schiefer wrote:
>>
>>> Is there a way to do branching and tagging in
workbench other  
>>> than the copy/cut and paste of the working
copy?
>>
>> Not at the moment. This will require a repository
browser facility  
>> that is not written yet.
>>
> What about the ability to copy to URL as a first step? 
No repo  
> browser facility required (though it would ultimately
be helpful.)

The same thought cross my mind. I'll add a command to allow
tagging  
and branching.
The project already knows about tags and branches for the
enhance log  
history. That
info can be used to default to copy.

>
>>>   The Workbench web page states that it
supports all client  
>>> operations, but I cannot find a way to get it
to perform copy or  
>>> move on a URL.  My repositories are managed in
the recommended  
>>> way with /trunk, /tags, and /branches and me
and my users always  
>>> just check out /trunk.  This cut and paste
interface is quite  
>>> klunky as it won't let me put a different
target name.  For  
>>> example, I want to copy my current /trunk to
/tags/some-example- 
>>> tag.  Right now I have to do this copy and
paste then rename / 
>>> tags/trunk to be /tags/some-example-tag.  All I
wanted to do was  
>>> tag my code in the repository!!!
>>>
>>
>> The Cut and Paste is great for rearranging files in
the working  
>> copy but
>> as you say not suitable as a tag/branch creation
method.
>>
>> In work flow that I use a work and for open source
projects I do  
>> not tag or branch
>> that often. All my projects have a script that I
run to tag a  
>> release and create a branch
>> to save having to remember the long URLs and to
check that the tag/ 
>> branch does
>> not already exist.
>>
> Ok...but it would be nice if Workbench was a 1-stop
shop for  
> everything.  The goal (at least for me and my
co-workers) when  
> using a tool is to have it as the sole tool we use. 
Requiring the  
> CLI to handle "normal" operations in a work
flow like branching and  
> tagging can be a real pain.  Is it on the roadmap to
allow copying  
> to/from URLs as supported in the CLI?

Yes I want to Workbench to be able to do URL copies etc.
I've  
implemented the frequently used operations first.

Barry

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribepysvn.tigris.org
For additional commands, e-mail: users-helppysvn.tigris.org

On Feb 18, 2007, at 17:34, Barry Scott wrote:

>
> On Feb 11, 2007, at 15:24, Larry Schiefer wrote:
>
>> Barry Scott wrote:
>>>
>>> On Feb 4, 2007, at 01:52, Larry Schiefer
wrote:
>>>
>>>> Is there a way to do branching and tagging
in workbench other  
>>>> than the copy/cut and paste of the working
copy?
>>>
>>> Not at the moment. This will require a
repository browser  
>>> facility that is not written yet.
>>>
>> What about the ability to copy to URL as a first
step?  No repo  
>> browser facility required (though it would
ultimately be helpful.)
>
> The same thought cross my mind. I'll add a command to
allow tagging  
> and branching.
> The project already knows about tags and branches for
the enhance  
> log history. That
> info can be used to default to copy.
>
>>
>>>>   The Workbench web page states that it
supports all client  
>>>> operations, but I cannot find a way to get
it to perform copy or  
>>>> move on a URL.  My repositories are managed
in the recommended  
>>>> way with /trunk, /tags, and /branches and
me and my users always  
>>>> just check out /trunk.  This cut and paste
interface is quite  
>>>> klunky as it won't let me put a different
target name.  For  
>>>> example, I want to copy my current /trunk
to /tags/some-example- 
>>>> tag.  Right now I have to do this copy and
paste then rename / 
>>>> tags/trunk to be /tags/some-example-tag. 
All I wanted to do was  
>>>> tag my code in the repository!!!
>>>>
>>>
>>> The Cut and Paste is great for rearranging
files in the working  
>>> copy but
>>> as you say not suitable as a tag/branch
creation method.
>>>
>>> In work flow that I use a work and for open
source projects I do  
>>> not tag or branch
>>> that often. All my projects have a script that
I run to tag a  
>>> release and create a branch
>>> to save having to remember the long URLs and to
check that the  
>>> tag/branch does
>>> not already exist.
>>>
>> Ok...but it would be nice if Workbench was a 1-stop
shop for  
>> everything.  The goal (at least for me and my
co-workers) when  
>> using a tool is to have it as the sole tool we use.
 Requiring the  
>> CLI to handle "normal" operations in a
work flow like branching  
>> and tagging can be a real pain.  Is it on the
roadmap to allow  
>> copying to/from URLs as supported in the CLI?
>
> Yes I want to Workbench to be able to do URL copies
etc. I've  
> implemented the frequently used operations first.
>
> Barry
>

r860 implements the Create Tag... and Create Branch...
commands.

Barry

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribepysvn.tigris.org
For additional commands, e-mail: users-helppysvn.tigris.org

Good stuff, thanks!

Larry

Barry Scott wrote:
> 
> On Feb 18, 2007, at 17:34, Barry Scott wrote:
> 
>>
>> On Feb 11, 2007, at 15:24, Larry Schiefer wrote:
>>
>>> Barry Scott wrote:
>>>>
>>>> On Feb 4, 2007, at 01:52, Larry Schiefer
wrote:
>>>>
>>>>> Is there a way to do branching and
tagging in workbench other than 
>>>>> the copy/cut and paste of the working
copy?
>>>>
>>>> Not at the moment. This will require a
repository browser facility 
>>>> that is not written yet.
>>>>
>>> What about the ability to copy to URL as a
first step?  No repo 
>>> browser facility required (though it would
ultimately be helpful.)
>>
>> The same thought cross my mind. I'll add a command
to allow tagging 
>> and branching.
>> The project already knows about tags and branches
for the enhance log 
>> history. That
>> info can be used to default to copy.
>>
>>>
>>>>>   The Workbench web page states that it
supports all client 
>>>>> operations, but I cannot find a way to
get it to perform copy or 
>>>>> move on a URL.  My repositories are
managed in the recommended way 
>>>>> with /trunk, /tags, and /branches and
me and my users always just 
>>>>> check out /trunk.  This cut and paste
interface is quite klunky as 
>>>>> it won't let me put a different target
name.  For example, I want 
>>>>> to copy my current /trunk to
/tags/some-example-tag.  Right now I 
>>>>> have to do this copy and paste then
rename /tags/trunk to be 
>>>>> /tags/some-example-tag.  All I wanted
to do was tag my code in the 
>>>>> repository!!!
>>>>>
>>>>
>>>> The Cut and Paste is great for rearranging
files in the working copy 
>>>> but
>>>> as you say not suitable as a tag/branch
creation method.
>>>>
>>>> In work flow that I use a work and for open
source projects I do not 
>>>> tag or branch
>>>> that often. All my projects have a script
that I run to tag a 
>>>> release and create a branch
>>>> to save having to remember the long URLs
and to check that the 
>>>> tag/branch does
>>>> not already exist.
>>>>
>>> Ok...but it would be nice if Workbench was a
1-stop shop for 
>>> everything.  The goal (at least for me and my
co-workers) when using 
>>> a tool is to have it as the sole tool we use. 
Requiring the CLI to 
>>> handle "normal" operations in a work
flow like branching and tagging 
>>> can be a real pain.  Is it on the roadmap to
allow copying to/from 
>>> URLs as supported in the CLI?
>>
>> Yes I want to Workbench to be able to do URL copies
etc. I've 
>> implemented the frequently used operations first.
>>
>> Barry
>>
> 
> r860 implements the Create Tag... and Create Branch...
commands.
> 
> Barry
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: users-unsubscribepysvn.tigris.org
> For additional commands, e-mail: users-helppysvn.tigris.org
> 
> 
> 
> 
> --No virus found in this incoming message.
> Checked by AVG Free Edition.Version: 7.5.467 / Virus
Database: 
> 269.8.0/817 - Release Date: 5/24/2007 4:01 PM
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: users-unsubscribepysvn.tigris.org
For additional commands, e-mail: users-helppysvn.tigris.org