You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Carmit Shiran <ca...@gmail.com> on 2012/09/05 10:24:53 UTC
problem with dialog box uisng Tortoisesvn
hello,
I downloaded Tortoisesvn to my computer.
I want the following command to be executed without opening the dialog box
at the end (I don't want the user to enter any data):
TortoiseProc.exe /command:commit /path:"C:\Projects\Widget3_Dev"
/closeonend:1
The /closeonend:1 doesn't seem to work. I still get the pop-up dialog.
I also tried changing the settings and switched the:
General->Dialogs 1-> Autoclose to : Auto-close if no errors.
But this also doesn't work.
Can you help me out?
What am I not doing right?
Thanks,
Carmit
RE: problem with dialog box uisng Tortoisesvn
Posted by "Cooke, Mark" <ma...@siemens.com>.
> -----Original Message-----
> From: Carmit Shiran [mailto:carmit.shiran@gmail.com]
> Sent: 05 September 2012 10:15
> To: Cooke, Mark
> Cc: users@subversion.apache.org
> Subject: Re: problem with dialog box uisng Tortoisesvn
>
> On Wed, Sep 5, 2012 at 11:43 AM, Cooke, Mark
> <ma...@siemens.com> wrote:
>
> > -----Original Message-----
> > From: Carmit Shiran [mailto:carmit.shiran@gmail.com]
> > Sent: 05 September 2012 09:25
> > To: users@subversion.apache.org
> > Subject: problem with dialog box uisng Tortoisesvn
> >
> > hello,
> > I downloaded Tortoisesvn to my computer.
> > I want the following command to be executed without opening
> > the dialog box at the end (I don't want the user to enter
> > any data):
> >
> > TortoiseProc.exe /command:commit
> > /path:"C:\Projects\Widget3_Dev" /closeonend:1
> >
> > The /closeonend:1 doesn't seem to work. I still get the
> > pop-up dialog.
> >
> > I also tried changing the settings and switched the:
> > General->Dialogs 1-> Autoclose to : Auto-close if no errors.
> >
> > But this also doesn't work.
> >
> > Can you help me out?
> > What am I not doing right?
> >
> > Thanks,
> > Carmit
>
>
> Why not just use the svn command line tools (they are
> an optional component when you install TortoiseSVN)? You
> could then call `svn commit`, see the on-line book help:-
>
> http://svnbook.red-bean.com/en/1.7/svn.tour.cycle.html#svn.tour.cycle.commit
>
> ~ mark c
>
> OK- I tired now:
>
> c:\Program files\TortoiseSVN\bin> $svn commit
>
> I got the following message:
> '$svn' is not recognized as an internal or external command,
> operable program or batch file.
>
> Where exaclty am I supposed to write this command. I dont'
> see in the book....
>
> In what path on the cmd line? Is this how to use it?
>
> Do I write $svn? or just svn (which also didn;t work for me)?
>
> Am I supposed to download anything else besides TortoiseSvn?
>
> (I downloaded it form http://tortoisesvn.net/downloads.html
> <http://tortoisesvn.net/downloads.html> , for 32-bit OS)
>
> I appreciate your help.
Have a look in `C:\Program Files\TortoiseSVN\bin`, do you have ~8 executables named e.g. `svn.exe`, `svnadmin.exe` ... `svnversion.exe`?
If not you probably need to re-run the TortoiseSVN installer and select the command line tools as they are an optional component. Note: it always helps to say which version you are using, I think older versions of Tortoise did not include the command line tools.
Once you have svn.exe installed and in your path, the command is just `svn` at a command line with options as specified in the excellent on-line book. For your example above, something like:
D:\> svn ci "C:\Projects\Widget3_Dev" -m "commit message text here"
The command `svn help` is also useful (in a command prompt).
~ mark c
RE: Problem with merging
Posted by John Maher <Jo...@rotair.com>.
Thanks Ryan, sent them a suggestion. Don't know if they'll like it, but
we'll find out.
John
-----Original Message-----
From: Ryan Schmidt [mailto:subversion-2012c@ryandesign.com]
Sent: Thursday, September 13, 2012 4:46 PM
To: John Maher
Cc: Stefan Sperling; users@subversion.apache.org
Subject: Re: Problem with merging
On Sep 13, 2012, at 08:23, John Maher wrote:
> How hard is it to change the book? I know what it means now, but the
> next person may get confused. I would bet that someone will
eventually
> get confused. If it said "repository tree" like the FAQ I would bet
it
> helps.
Book feedback should be sent to the book's authors. Go to:
http://svnbook.org/
and scroll down to the "Feedback/Contributing" heading.
Re: Problem with merging
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 13, 2012, at 08:23, John Maher wrote:
> How hard is it to change the book? I know what it means now, but the
> next person may get confused. I would bet that someone will eventually
> get confused. If it said "repository tree" like the FAQ I would bet it
> helps.
Book feedback should be sent to the book's authors. Go to:
http://svnbook.org/
and scroll down to the "Feedback/Contributing" heading.
RE: Problem with merging
Posted by John Maher <Jo...@rotair.com>.
Thank you Stefan. Very helpful.
John
-----Original Message-----
From: Stefan Sperling [mailto:stsp@elego.de]
Sent: Friday, September 14, 2012 10:24 AM
To: John Maher
Cc: users@subversion.apache.org
Subject: Re: Problem with merging
On Thu, Sep 13, 2012 at 09:23:54AM -0400, John Maher wrote:
> How hard is it to change the book?
Check out the book sources, make changes, and either send a
patch (i.e. the output of "svn diff" showing your changes) to
the svnbook development list, or file an issue in the book's
issue tracker and attach the patch to the issue.
You can create a patch file like this from the top of your
book sources working copy:
svn diff > my-changes.patch
See "Feedback / Contributing" on http://svnbook.red-bean.com/
for more information.
If you want to compile your edited book sources before submitting
your changes, which is a good idea in case you're not just making
simple tweaks to the text but also add or change XML tags, see
http://svnbook.googlecode.com/svn/trunk/en/README
Re: Problem with merging
Posted by Stefan Sperling <st...@elego.de>.
On Thu, Sep 13, 2012 at 09:23:54AM -0400, John Maher wrote:
> How hard is it to change the book?
Check out the book sources, make changes, and either send a
patch (i.e. the output of "svn diff" showing your changes) to
the svnbook development list, or file an issue in the book's
issue tracker and attach the patch to the issue.
You can create a patch file like this from the top of your
book sources working copy:
svn diff > my-changes.patch
See "Feedback / Contributing" on http://svnbook.red-bean.com/
for more information.
If you want to compile your edited book sources before submitting
your changes, which is a good idea in case you're not just making
simple tweaks to the text but also add or change XML tags, see
http://svnbook.googlecode.com/svn/trunk/en/README
RE: Problem with merging
Posted by John Maher <Jo...@rotair.com>.
Thanks Stefan.
I did read most of the links. I didn't know about the FAQ, thanks.
Your statement was key:
"Note that the "tree" being talked about there is not an individual
branch, but all nodes in the repository, including the /trunk directory
and the /branches/feature directory."
Basically in the book in that section tree means repository. But you
cleared it up and the FAQ helped because the fact calls it the
repository tree.
How hard is it to change the book? I know what it means now, but the
next person may get confused. I would bet that someone will eventually
get confused. If it said "repository tree" like the FAQ I would bet it
helps.
John
Re: Problem with merging
Posted by Stefan Sperling <st...@elego.de>.
On Wed, Sep 12, 2012 at 01:39:41PM -0400, John Maher wrote:
> Here's what I did:
Hi John,
your questions are about fundamental Subversion concepts, and
that's fine. Just please understand that I don't want to type
another explanation since good documentation has already been
written. So, below, I'll throw you some links to the FAQ and
the Subversion book for further reading, hoping that these will
answer your questions.
> 1. Create repository on the server called "test" with trunk and
> branches directories.
> 2. Issue the command G:\Code\st>svn checkout
> https://server.com/svn/test/trunk .
> 3. Added the project using tortoise (14 files/directories).
> 4. Made a change to the project.
> 5. Issue the command G:\Code\st>svn commit -m "Two"
> Adding WindowsApplication1
> Adding WindowsApplication1\Form1.Designer.vb
> Adding WindowsApplication1\Form1.resx
> Adding WindowsApplication1\Form1.vb
> Adding WindowsApplication1\My Project
> Adding WindowsApplication1\My Project\Application.Designer.vb
> Adding WindowsApplication1\My Project\Application.myapp
> Adding WindowsApplication1\My Project\AssemblyInfo.vb
> Adding WindowsApplication1\My Project\Resources.Designer.vb
> Adding WindowsApplication1\My Project\Resources.resx
> Adding WindowsApplication1\My Project\Settings.Designer.vb
> Adding WindowsApplication1\My Project\Settings.settings
> Adding WindowsApplication1\WindowsApplication1.sln
> Adding WindowsApplication1\WindowsApplication1.vbproj
> Transmitting file data ............
> Committed revision 2.
> 6. Made a change to the project.
> 7. Issue the command G:\Code\st>svn commit -m "Three"
> Sending WindowsApplication1\Form1.Designer.vb
> Transmitting file data .
> Committed revision 3.
> 8. Made a change to the project to simulate a feature.
> 9. Issue the command G:\Code\st>svn commit -m "Four"
> Sending WindowsApplication1\Form1.Designer.vb
> Transmitting file data .
> Committed revision 4.
> 10. Issue the command G:\Code\st>svn copy
> https://server.com/svn/test/trunk
> https://server.com/svn/test/branches/feature -m "Feature"
> Committed revision 5.
> 11. Changed the current directory from st (subversion test) to stb
> (subversion test branch.
> 12. Issue the command G:\Code\stb>svn checkout
> https://server.com/svn/test/branches/feature .
> A WindowsApplication1
> A WindowsApplication1\WindowsApplication1.vbproj
> A WindowsApplication1\Form1.resx
> A WindowsApplication1\Form1.Designer.vb
> A WindowsApplication1\Form1.vb
> A WindowsApplication1\WindowsApplication1.sln
> A WindowsApplication1\My Project
> A WindowsApplication1\My Project\Resources.Designer.vb
> A WindowsApplication1\My Project\Settings.settings
> A WindowsApplication1\My Project\AssemblyInfo.vb
> A WindowsApplication1\My Project\Settings.Designer.vb
> A WindowsApplication1\My Project\Application.Designer.vb
> A WindowsApplication1\My Project\Application.myapp
> A WindowsApplication1\My Project\Resources.resx
> Checked out revision 5.
> 13. Made a change to the feature branch.
> 14. Issue the command G:\Code\stb>svn commit -m "Six-feature"
> Sending WindowsApplication1\Form1.Designer.vb
> Transmitting file data .
> Committed revision 6.
> 15. Changed the current directory from stb to st.
> 16. Made a change to the project to simulate a bug fix.
> 17. Issue the command G:\Code\st>svn commit -m "Five-bug fix"
> Sending WindowsApplication1\Form1.Designer.vb
> Transmitting file data .
> Committed revision 7.
> *** Why 7?
See http://svnbook.red-bean.com/en/1.7/svn.basic.in-action.html#svn.basic.in-action.revs
and http://subversion.apache.org/faq.html#globalrev
Note that the "tree" being talked about there is not an individual
branch, but all nodes in the repository, including the /trunk directory
and the /branches/feature directory.
> 18. Changed the current directory from st to stb to try to merge the
> bug fix to the feature branch.
> 19. Issue the command G:\Code\stb>svn merge
> https://server.com/svn/test/trunk --dry-run
> svn: E195020: Cannot merge into mixed-revision working copy [5:6]; try
> updating first
> *** Why update? No one else is doing anything!!
Please see
http://svnbook.red-bean.com/en/1.7/svn.basic.in-action.html#svn.basic.in-action.mixedrevs
and http://subversion.apache.org/faq.html#hidden-log
> 20. Issue the command G:\Code\stb>svn update
> Updating '.':
> At revision 7.
> *** Why go to 7?
See above.
> 21. Issue the command G:\Code\stb>svn diff -r6:7
> (Nothing returned using -r5:7 displays the changes I made)
> 22. Issue the command G:\Code\stb>svn merge
> https://server.com/svn/test/trunk --dry-run
> --- Merging r5 through r7 into '.':
> C WindowsApplication1\Form1.Designer.vb
> Summary of conflicts:
> Text conflicts: 1
> What does that mean?
See http://svnbook.red-bean.com/en/1.7/svn.tour.cycle.html#svn.tour.cycle.resolve
Re: Problem with merging
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
John Maher wrote on Thu, Sep 13, 2012 at 10:26:39 -0400:
> Yes that is what I did. Now that I know that causes problems with the
> subversion mailing list I won't do it again.
>
For completeness...
http://subversion.apache.org/docs/community-guide/mailing-lists#fresh-post
Re: Problem with merging
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag John Maher,
am Donnerstag, 13. September 2012 um 16:26 schrieben Sie:
> Yes that is what I did. Now that I know that causes problems with the
> subversion mailing list I won't do it again.
It causes problems on nearly every mailing list as they each work
similar. The first mail you sent has a "References" header referring
the mail you answered to and changed the subject, new mails don't.
That's what most mail clients etc. use to identify and build threads.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Problem with merging
Posted by Giulio Troccoli <gi...@mediatelgroup.co.uk>.
On 13/09/12 15:26, John Maher wrote:
> Yes that is what I did. Now that I know that causes problems with the
> subversion mailing list I won't do it again.
>
> John
>
Thank you
Giulio
RE: Problem with merging
Posted by John Maher <Jo...@rotair.com>.
Yes that is what I did. Now that I know that causes problems with the
subversion mailing list I won't do it again.
John
-----Original Message-----
From: Giulio Troccoli [mailto:giulio.troccoli@mediatelgroup.co.uk]
Sent: Thursday, September 13, 2012 10:25 AM
To: John Maher
Cc: users@subversion.apache.org
Subject: Re: Problem with merging
On 13/09/12 15:15, John Maher wrote:
> Can you tell me what that means? I had a question on merging so I
sent
> it to the mailing list. Are you saying I'm not supposed to do that?
If
> not then can you explain the procedure?
You are hijacking someone else's email. Presumably you have clicked on
Reply or ReplyAll to a previous email and changed the subject and text.
Unfortunately this means that your email is going in the same thread as
the one you replied to, which is not related to your problem. When
asking a new question simply send a new email, don't reply to one.
I hope I was clearer now.
Giulio
Re: Problem with merging
Posted by Giulio Troccoli <gi...@mediatelgroup.co.uk>.
On 13/09/12 15:15, John Maher wrote:
> Can you tell me what that means? I had a question on merging so I sent
> it to the mailing list. Are you saying I'm not supposed to do that? If
> not then can you explain the procedure?
You are hijacking someone else's email. Presumably you have clicked on
Reply or ReplyAll to a previous email and changed the subject and text.
Unfortunately this means that your email is going in the same thread as
the one you replied to, which is not related to your problem. When
asking a new question simply send a new email, don't reply to one.
I hope I was clearer now.
Giulio
RE: Problem with merging
Posted by John Maher <Jo...@rotair.com>.
Can you tell me what that means? I had a question on merging so I sent
it to the mailing list. Are you saying I'm not supposed to do that? If
not then can you explain the procedure?
John
-----Original Message-----
From: Giulio Troccoli [mailto:giulio.troccoli@mediatelgroup.co.uk]
Sent: Thursday, September 13, 2012 4:56 AM
To: John Maher
Cc: users@subversion.apache.org
Subject: Re: Problem with merging
On 12/09/12 18:39, John Maher wrote:
> Hello
[CUT]
Can you please stop reusing an already existing thread and instead start
a new one for a new question?
> Thanks
> John
Thanks
Giulio
Re: Problem with merging
Posted by Giulio Troccoli <gi...@mediatelgroup.co.uk>.
On 12/09/12 18:39, John Maher wrote:
> Hello
[CUT]
Can you please stop reusing an already existing thread and instead start
a new one for a new question?
> Thanks
> John
Thanks
Giulio
Re: Problem with merging
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag John Maher,
am Donnerstag, 13. September 2012 um 15:35 schrieben Sie:
> In reality we should've had code control a long time ago. I only
> got here a few years ago. And when I first got here I met extreme
> resistance about incorporating something like subversion. I finally
> got the green light, quite possibly because they didn't have to
> spend any money. Now I must learn to use it. :)
Prepare yourself for the day you loose a repository. I had a lot of
fun explaining my manager why I'm working two days on restoring things
from our corrupted NTFS file system and why it's worth the time to not
just drop version control. :-)
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
RE: Problem with merging
Posted by John Maher <Jo...@rotair.com>.
Thanks Thorsten.
While its true that I didn't technically lose code, it was probably in there somewhere. The loss was discovered weeks later and we have a lot of code. It would take days going over everything then we would have to *hope* we got everything. Some things would let us know if we missed them, others things may not. We could go days or weeks before we noticed we were losing data. Since we were a few weeks away from the next release I decided to put off updating production. Basically it would cost too much to possibly not get all the code sprinkled with a slim chance of data loss. So from a business perspective, the code was lost.
In reality we should've had code control a long time ago. I only got here a few years ago. And when I first got here I met extreme resistance about incorporating something like subversion. I finally got the green light, quite possibly because they didn't have to spend any money. Now I must learn to use it. :)
Revisions are global is what I needed to know, thanks.
John
-----Original Message-----
From: Thorsten Schöning [mailto:tschoening@am-soft.de]
Sent: Wednesday, September 12, 2012 2:39 PM
To: users@subversion.apache.org
Subject: Re: Problem with merging
Guten Tag John Maher,
am Mittwoch, 12. September 2012 um 19:39 schrieben Sie:
> I started using subversion a while back and doing a merge I lost a bunch
> of source code which prohibited me from updating production for weeks.
Unless you didn't commit, you can't loose source code, that's what
version control is all about. Even if you didn't commit Subversion
would always try everything to preserve your current modifications,
which may result in the conflicts you describe later. The easiest way
to never ever loose anything it always commit before doing any
changes to your working copy like merges and whatever goes wrong after
a commit can be restored.
> I now have a stable code base and wish to use subversion so I tried to
> follow chapter 4, branching and merging. It failed.
If you mean your later mentioned conflicts with "failed", this isn't
exactly true, as a conflict is a normal operation and the merge may
succeed. Conflicts only mean that there are changes which Subversion
can't merge automatically safely and the user needs to do something to
merge the changes. This is not the same as an error during the merge
or else.
> 1) I was on revision 4. I then branced it, made a change and it
> jumped to revision 7. Why? Does the revision apply to all folders
> under a repository?
Yes, revisions are global, that's one of the fundamental concepts of
Subversion and is normally considered as a major benefit over previous
centralized version control like CVS.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: Problem with merging
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag John Maher,
am Mittwoch, 12. September 2012 um 19:39 schrieben Sie:
> I started using subversion a while back and doing a merge I lost a bunch
> of source code which prohibited me from updating production for weeks.
Unless you didn't commit, you can't loose source code, that's what
version control is all about. Even if you didn't commit Subversion
would always try everything to preserve your current modifications,
which may result in the conflicts you describe later. The easiest way
to never ever loose anything it always commit before doing any
changes to your working copy like merges and whatever goes wrong after
a commit can be restored.
> I now have a stable code base and wish to use subversion so I tried to
> follow chapter 4, branching and merging. It failed.
If you mean your later mentioned conflicts with "failed", this isn't
exactly true, as a conflict is a normal operation and the merge may
succeed. Conflicts only mean that there are changes which Subversion
can't merge automatically safely and the user needs to do something to
merge the changes. This is not the same as an error during the merge
or else.
> 1) I was on revision 4. I then branced it, made a change and it
> jumped to revision 7. Why? Does the revision apply to all folders
> under a repository?
Yes, revisions are global, that's one of the fundamental concepts of
Subversion and is normally considered as a major benefit over previous
centralized version control like CVS.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Problem with merging
Posted by John Maher <Jo...@rotair.com>.
Hello
I started using subversion a while back and doing a merge I lost a bunch
of source code which prohibited me from updating production for weeks.
I now have a stable code base and wish to use subversion so I tried to
follow chapter 4, branching and merging. It failed. I was hoping
someone could tell me what I am doing wrong. I went through the process
twice and got the same result, so at least I make the same mistake
consistently. There are a couple of weird unexplained behaviors I am
noting along with a log of what I did.
1) I was on revision 4. I then branced it, made a change and it
jumped to revision 7. Why? Does the revision apply to all folders
under a repository?
2) I made a change to the branch, commited it to revision 6. Then
made a change to the trunk to revision 7 (from 4). Then I tried to
merge the change from the trunk to the branch and it required an update.
Why?
3) Now it says text conflict. What does that mean?
Is there another section in the book that may explain merging? Another
read? I would like to get subversion working without any more code
loss.
Here's what I did:
1. Create repository on the server called "test" with trunk and
branches directories.
2. Issue the command G:\Code\st>svn checkout
https://server.com/svn/test/trunk .
3. Added the project using tortoise (14 files/directories).
4. Made a change to the project.
5. Issue the command G:\Code\st>svn commit -m "Two"
Adding WindowsApplication1
Adding WindowsApplication1\Form1.Designer.vb
Adding WindowsApplication1\Form1.resx
Adding WindowsApplication1\Form1.vb
Adding WindowsApplication1\My Project
Adding WindowsApplication1\My Project\Application.Designer.vb
Adding WindowsApplication1\My Project\Application.myapp
Adding WindowsApplication1\My Project\AssemblyInfo.vb
Adding WindowsApplication1\My Project\Resources.Designer.vb
Adding WindowsApplication1\My Project\Resources.resx
Adding WindowsApplication1\My Project\Settings.Designer.vb
Adding WindowsApplication1\My Project\Settings.settings
Adding WindowsApplication1\WindowsApplication1.sln
Adding WindowsApplication1\WindowsApplication1.vbproj
Transmitting file data ............
Committed revision 2.
6. Made a change to the project.
7. Issue the command G:\Code\st>svn commit -m "Three"
Sending WindowsApplication1\Form1.Designer.vb
Transmitting file data .
Committed revision 3.
8. Made a change to the project to simulate a feature.
9. Issue the command G:\Code\st>svn commit -m "Four"
Sending WindowsApplication1\Form1.Designer.vb
Transmitting file data .
Committed revision 4.
10. Issue the command G:\Code\st>svn copy
https://server.com/svn/test/trunk
https://server.com/svn/test/branches/feature -m "Feature"
Committed revision 5.
11. Changed the current directory from st (subversion test) to stb
(subversion test branch.
12. Issue the command G:\Code\stb>svn checkout
https://server.com/svn/test/branches/feature .
A WindowsApplication1
A WindowsApplication1\WindowsApplication1.vbproj
A WindowsApplication1\Form1.resx
A WindowsApplication1\Form1.Designer.vb
A WindowsApplication1\Form1.vb
A WindowsApplication1\WindowsApplication1.sln
A WindowsApplication1\My Project
A WindowsApplication1\My Project\Resources.Designer.vb
A WindowsApplication1\My Project\Settings.settings
A WindowsApplication1\My Project\AssemblyInfo.vb
A WindowsApplication1\My Project\Settings.Designer.vb
A WindowsApplication1\My Project\Application.Designer.vb
A WindowsApplication1\My Project\Application.myapp
A WindowsApplication1\My Project\Resources.resx
Checked out revision 5.
13. Made a change to the feature branch.
14. Issue the command G:\Code\stb>svn commit -m "Six-feature"
Sending WindowsApplication1\Form1.Designer.vb
Transmitting file data .
Committed revision 6.
15. Changed the current directory from stb to st.
16. Made a change to the project to simulate a bug fix.
17. Issue the command G:\Code\st>svn commit -m "Five-bug fix"
Sending WindowsApplication1\Form1.Designer.vb
Transmitting file data .
Committed revision 7.
*** Why 7?
18. Changed the current directory from st to stb to try to merge the
bug fix to the feature branch.
19. Issue the command G:\Code\stb>svn merge
https://server.com/svn/test/trunk --dry-run
svn: E195020: Cannot merge into mixed-revision working copy [5:6]; try
updating first
*** Why update? No one else is doing anything!!
20. Issue the command G:\Code\stb>svn update
Updating '.':
At revision 7.
*** Why go to 7?
21. Issue the command G:\Code\stb>svn diff -r6:7
(Nothing returned using -r5:7 displays the changes I made)
22. Issue the command G:\Code\stb>svn merge
https://server.com/svn/test/trunk --dry-run
--- Merging r5 through r7 into '.':
C WindowsApplication1\Form1.Designer.vb
Summary of conflicts:
Text conflicts: 1
What does that mean?
Thanks
John
Re: problem with dialog box uisng Tortoisesvn
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Please start a new thread for unrelated problems:
http://subversion.apache.org/docs/community-guide/mailing-lists#fresh-post
You should probably say a bit more about your situation in order to get
a more specific reply. If you just want anonymous unencrypted access,
it'll be easiest to set up svnserve --- either tortoise or several of
the options in http://subversion.apache.org/packages#windows will wrap
that for you.
Daniel
Carmit Shiran wrote on Wed, Oct 10, 2012 at 12:13:02 +0200:
> Hi all,
>
> Does anyone know how can I access my local repository on my computer from a
> different computer?
> I installed the TortoiseSVN locally on my computer.
> Thanks
>
>
>
> On at, Sep 15, 2012 at 12:23 AM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
>
> > Carmit Shiran wrote on Wed, Sep 12, 2012 at 13:12:52 +0200:
> > > If you look at my example I sent in the previous email, you can see I
> > > filled in the argument= $target_path :
> > > my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
> > > But I'm looking for a way to fill it automatically with the "current
> > > path/tag".
> > > Is it possible?
> >
> > Have a look at svn:keywords. Something like
> >
> > my $foo = <<'EOF';
> > $URL$
> > EOF
> >
> > is probably the best readable.
> >
> >
> >
> > And if no one said that already, remember that if you share a repository
> > with other people it's recommended _not_ to use file://.
> >
Re: problem with dialog box uisng Tortoisesvn
Posted by Carmit Shiran <ca...@gmail.com>.
Hi all,
Does anyone know how can I access my local repository on my computer from a
different computer?
I installed the TortoiseSVN locally on my computer.
Thanks
On at, Sep 15, 2012 at 12:23 AM, Daniel Shahaf <d....@daniel.shahaf.name>wrote:
> Carmit Shiran wrote on Wed, Sep 12, 2012 at 13:12:52 +0200:
> > If you look at my example I sent in the previous email, you can see I
> > filled in the argument= $target_path :
> > my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
> > But I'm looking for a way to fill it automatically with the "current
> > path/tag".
> > Is it possible?
>
> Have a look at svn:keywords. Something like
>
> my $foo = <<'EOF';
> $URL$
> EOF
>
> is probably the best readable.
>
>
>
> And if no one said that already, remember that if you share a repository
> with other people it's recommended _not_ to use file://.
>
Re: problem with dialog box uisng Tortoisesvn
Posted by Daniel Shahaf <d....@daniel.shahaf.name>.
Carmit Shiran wrote on Wed, Sep 12, 2012 at 13:12:52 +0200:
> If you look at my example I sent in the previous email, you can see I
> filled in the argument= $target_path :
> my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
> But I'm looking for a way to fill it automatically with the "current
> path/tag".
> Is it possible?
Have a look at svn:keywords. Something like
my $foo = <<'EOF';
$URL$
EOF
is probably the best readable.
And if no one said that already, remember that if you share a repository
with other people it's recommended _not_ to use file://.
Re: problem with dialog box uisng Tortoisesvn
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Carmit Shiran,
am Mittwoch, 12. September 2012 um 13:12 schrieben Sie:
> If you look at my example I sent in the previous email, you can see I
> filled in the argument= $target_path :
> my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
> But I'm looking for a way to fill it automatically with the "current
> path/tag".
> Is it possible?
It depends on where you run your command, if its in the current
working copy, you may just replace your target with relative paths
like in "svn cp . ../somewhere/to/tag".
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
Re: problem with dialog box uisng Tortoisesvn
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 12, 2012, at 06:12, Carmit Shiran <ca...@gmail.com> wrote:
> Do you know if there's a way to know what is the current tag I'm working on? Meaning: If I want to use 'svn copy' on the file I'm working on now without sending the argument of the source file but only the tag name, is it possible to send the 'current file path' as the first argument?
> For instance, if the user doesn't know on what tag he's working on, assuming he's not working on the 'trunk' but rather on 'tag= Release_60'. And now he wants to copy 'Release_60' to 'Release_61'. But he doesn't know he's working on 'Release_60'. How do I find out using svn command lines?
The user runs "svn info" and examines the output to discover what tag he's working on.
Usually one wouldn't be "working on" a tag though. Tags are supposed to be considered as read-only entities. You "work on" branches or trunk.
> If you look at my example I sent in the previous email, you can see I filled in the argument= $target_path :
> my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
> But I'm looking for a way to fill it automatically with the "current path/tag".
> Is it possible?
Sure, you could write a script to extract that information out of "svn info".
Re: problem with dialog box uisng Tortoisesvn
Posted by Carmit Shiran <ca...@gmail.com>.
Thanks! It works for me now!
another short question:
Do you know if there's a way to know what is the current tag I'm working
on? Meaning: If I want to use 'svn copy' on the file I'm working on now
without sending the argument of the source file but only the tag name, is
it possible to send the 'current file path' as the first argument?
For instance, if the user doesn't know on what tag he's working on,
assuming he's not working on the 'trunk' but rather on 'tag= Release_60'.
And now he wants to copy 'Release_60' to 'Release_61'. But he doesn't know
he's working on 'Release_60'. How do I find out using svn command lines?
If you look at my example I sent in the previous email, you can see I
filled in the argument= $target_path :
my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
But I'm looking for a way to fill it automatically with the "current
path/tag".
Is it possible?
Thanks a lot!
have a great day!
On Wed, Sep 12, 2012 at 12:10 PM, Tony Sweeney <ts...@omnifone.com>wrote:
> **
>
>
> ------------------------------
> *From:* Carmit Shiran [mailto:carmit.shiran@gmail.com]
> *Sent:* 12 September 2012 08:14
> *To:* Ryan Schmidt
> *Cc:* Cooke, Mark; users@subversion.apache.org
> *Subject:* Re: problem with dialog box uisng Tortoisesvn
>
> thanks for your help.
> Seems like I didn't have the whole svn package.
> I reinstalled the svn and made sure I pick the "command tool" and now the
> svn commands work for me.
>
> Though I have a problem with the tag command:
>
> I wrote a script in perl:
> my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
> my $tag = "file:///C:/svn_repos3/tags/Release_63"
>
> system ("svn copy -m \"tagging the file\" \"$target_path\" \"$tag\" ");
>
> and got the following error:
>
> svn: E160005: Invalid control character '0X0a' in path 'Release_63\012'
>
> Does anyone know what this error is?
>
> That's just a line feed at the end of one of your variable strings. Use
> chomp to get rid of it and you should be golden.
>
> Tony.
>
> thanks!!
>
>
>
> On Wed, Sep 5, 2012 at 1:21 PM, Ryan Schmidt <
> subversion-2012c@ryandesign.com> wrote:
>
>>
>> On Sep 5, 2012, at 04:14, Carmit Shiran wrote:
>>
>> > c:\Program files\TortoiseSVN\bin> $svn commit
>> >
>> > I got the following message:
>> > '$svn' is not recognized as an internal or external command, operable
>> program or batch file.
>>
>> You're not supposed to type "$". We just use "$" to indicate "type the
>> things after this". It's a fairly common character for a command prompt.
>> This same convention is used by the SVN Book [1], which is a good document
>> to read to get familiar with how to use Subversion.
>>
>>
>> [1] http://svnbook.org/
>>
>>
>>
>>
>>
>>
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
> ------------------------------
>
> No virus found in this message.
> Checked by AVG - www.avg.com
> Version: 2012.0.2221 / Virus Database: 2437/5262 - Release Date: 09/11/12
>
> ______________________________________________________________________
> This email has been scanned by the Symantec Email Security.cloud service.
> For more information please visit http://www.symanteccloud.com
> ______________________________________________________________________
>
RE: problem with dialog box uisng Tortoisesvn
Posted by Tony Sweeney <ts...@omnifone.com>.
________________________________
From: Carmit Shiran [mailto:carmit.shiran@gmail.com]
Sent: 12 September 2012 08:14
To: Ryan Schmidt
Cc: Cooke, Mark; users@subversion.apache.org
Subject: Re: problem with dialog box uisng Tortoisesvn
thanks for your help.
Seems like I didn't have the whole svn package.
I reinstalled the svn and made sure I pick the "command tool" and now the svn commands work for me.
Though I have a problem with the tag command:
I wrote a script in perl:
my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
my $tag = "file:///C:/svn_repos3/tags/Release_63"
system ("svn copy -m \"tagging the file\" \"$target_path\" \"$tag\" ");
and got the following error:
svn: E160005: Invalid control character '0X0a' in path 'Release_63\012'
Does anyone know what this error is?
That's just a line feed at the end of one of your variable strings. Use chomp to get rid of it and you should be golden.
Tony.
thanks!!
On Wed, Sep 5, 2012 at 1:21 PM, Ryan Schmidt <su...@ryandesign.com>> wrote:
On Sep 5, 2012, at 04:14, Carmit Shiran wrote:
> c:\Program files\TortoiseSVN\bin> $svn commit
>
> I got the following message:
> '$svn' is not recognized as an internal or external command, operable program or batch file.
You're not supposed to type "$". We just use "$" to indicate "type the things after this". It's a fairly common character for a command prompt. This same convention is used by the SVN Book [1], which is a good document to read to get familiar with how to use Subversion.
[1] http://svnbook.org/
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
________________________________
No virus found in this message.
Checked by AVG - www.avg.com<http://www.avg.com>
Version: 2012.0.2221 / Virus Database: 2437/5262 - Release Date: 09/11/12
______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
For more information please visit http://www.symanteccloud.com
______________________________________________________________________
Re: problem with dialog box uisng Tortoisesvn
Posted by Carmit Shiran <ca...@gmail.com>.
thanks for your help.
Seems like I didn't have the whole svn package.
I reinstalled the svn and made sure I pick the "command tool" and now the
svn commands work for me.
Though I have a problem with the tag command:
I wrote a script in perl:
my $target_path = "file:///C:/svn_repos3/trunk/Widget3"
my $tag = "file:///C:/svn_repos3/tags/Release_63"
system ("svn copy -m \"tagging the file\" \"$target_path\" \"$tag\" ");
and got the following error:
svn: E160005: Invalid control character '0X0a' in path 'Release_63\012'
Does anyone know what this error is?
thanks!!
On Wed, Sep 5, 2012 at 1:21 PM, Ryan Schmidt <
subversion-2012c@ryandesign.com> wrote:
>
> On Sep 5, 2012, at 04:14, Carmit Shiran wrote:
>
> > c:\Program files\TortoiseSVN\bin> $svn commit
> >
> > I got the following message:
> > '$svn' is not recognized as an internal or external command, operable
> program or batch file.
>
> You're not supposed to type "$". We just use "$" to indicate "type the
> things after this". It's a fairly common character for a command prompt.
> This same convention is used by the SVN Book [1], which is a good document
> to read to get familiar with how to use Subversion.
>
>
> [1] http://svnbook.org/
>
>
>
>
>
>
Re: problem with dialog box uisng Tortoisesvn
Posted by Ryan Schmidt <su...@ryandesign.com>.
On Sep 5, 2012, at 04:14, Carmit Shiran wrote:
> c:\Program files\TortoiseSVN\bin> $svn commit
>
> I got the following message:
> '$svn' is not recognized as an internal or external command, operable program or batch file.
You're not supposed to type "$". We just use "$" to indicate "type the things after this". It's a fairly common character for a command prompt. This same convention is used by the SVN Book [1], which is a good document to read to get familiar with how to use Subversion.
[1] http://svnbook.org/
Re: problem with dialog box uisng Tortoisesvn
Posted by Ulrich Eckhardt <ul...@dominolaser.com>.
Am 05.09.2012 11:14, schrieb Carmit Shiran:
> Where exaclty am I supposed to write this command. I dont' see in the
> book....
>
> In what path on the cmd line? Is this how to use it?
>
> Do I write $svn? or just svn (which also didn;t work for me)?
Others already suggested that you check whether the commandline tools
are installed as part of TortoiseSVN. In addition a few suggestions:
1. MS Windows looks for executables in the current working directory, so
if you can call it from "C:\Program Files\TortoiseSVN\bin". Other than
that, it looks for things using the PATH environment variable. Look for
"PATH environment" and your OS online to find out more about this. This
enables you to open a command prompt anywhere and run SVN from that.
2. If you want to automate things, there is a third option and that is
to use one of various SVN Client APIs. If you just want to run a few
commands automatically now and then, it probably isn't worth it, but if
you require more complex operations it will.
> Am I supposed to download anything else besides TortoiseSvn?
No, TSVN includes the TortoiseSVN client but also the normal commandline
client. The latter is optional though, so you might have to rerun the
installation to get it. It is possible that this also sets the PATH
environment variable as part of the installation then, but I'm not sure.
Good luck!
Uli
**************************************************************************************
Domino Laser GmbH, Fangdieckstraße 75a, 22547 Hamburg, Deutschland
Geschäftsführer: Thorsten Föcking, Amtsgericht Hamburg HR B62 932
**************************************************************************************
Visit our website at http://www.dominolaser.com
**************************************************************************************
Diese E-Mail einschließlich sämtlicher Anhänge ist nur für den Adressaten bestimmt und kann vertrauliche Informationen enthalten. Bitte benachrichtigen Sie den Absender umgehend, falls Sie nicht der beabsichtigte Empfänger sein sollten. Die E-Mail ist in diesem Fall zu löschen und darf weder gelesen, weitergeleitet, veröffentlicht oder anderweitig benutzt werden.
E-Mails können durch Dritte gelesen werden und Viren sowie nichtautorisierte Änderungen enthalten. Domino Laser GmbH ist für diese Folgen nicht verantwortlich.
**************************************************************************************
Re: problem with dialog box uisng Tortoisesvn
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Carmit Shiran,
am Mittwoch, 5. September 2012 um 11:14 schrieben Sie:
> I got the following message:
> '$svn' is not recognized as an internal or external command, operable
> program or batch file.
$svn of course is not an executable or why didn't you call
$TortoiseProc.exe?
> Where exaclty am I supposed to write this command.
On the command line, as it's a command line client.
> In what path on the cmd line? Is this how to use it?
Wherever you installed it.
> Do I write $svn? or just svn (which also didn;t work for me)?
Maybe the command line client is not installed, as it isn't by
default. Check your Tortoise installation and modify it as necessary
to include the command line. Afterwards have a look at the Tortoise
installation directory to see where svn.exe is installed.
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow
RE: problem with dialog box uisng Tortoisesvn
Posted by Bert Huijben <be...@qqmail.nl>.
$ svn ci -m "comment"
Is a common way for documentation to tell that you should type exactly what
is behind the $. The '$' itself is a placeholder for your prompt which could
be something like 'C:\Windows>' on Windows or something like '~/svn-site
(bert@host)' on another system.
If you leave out the $ and installed the commandline binaries things should
work for you.
Bert
PS. Please use plain text on this mailing list as that makes it much
easier/possible to answer in-line.
From: Carmit Shiran [mailto:carmit.shiran@gmail.com]
Sent: woensdag 5 september 2012 11:15
To: Cooke, Mark
Cc: users@subversion.apache.org
Subject: Re: problem with dialog box uisng Tortoisesvn
On Wed, Sep 5, 2012 at 11:43 AM, Cooke, Mark <ma...@siemens.com> wrote:
> -----Original Message-----
> From: Carmit Shiran [mailto:carmit.shiran@gmail.com]
> Sent: 05 September 2012 09:25
> To: users@subversion.apache.org
> Subject: problem with dialog box uisng Tortoisesvn
>
> hello,
> I downloaded Tortoisesvn to my computer.
> I want the following command to be executed without opening
> the dialog box at the end (I don't want the user to enter any data):
>
> TortoiseProc.exe /command:commit
> /path:"C:\Projects\Widget3_Dev" /closeonend:1
>
> The /closeonend:1 doesn't seem to work. I still get the pop-up dialog.
>
> I also tried changing the settings and switched the:
> General->Dialogs 1-> Autoclose to : Auto-close if no errors.
>
> But this also doesn't work.
>
> Can you help me out?
> What am I not doing right?
>
> Thanks,
> Carmit
Why not just use the svn command line tools (they are an optional component
when you install TortoiseSVN)? You could then call `svn commit`, see the
on-line book help:-
http://svnbook.red-bean.com/en/1.7/svn.tour.cycle.html#svn.tour.cycle.commit
~ mark c
OK- I tired now:
c:\Program files\TortoiseSVN\bin> $svn commit
I got the following message:
'$svn' is not recognized as an internal or external command, operable
program or batch file.
Where exaclty am I supposed to write this command. I dont' see in the
book....
In what path on the cmd line? Is this how to use it?
Do I write $svn? or just svn (which also didn;t work for me)?
Am I supposed to download anything else besides TortoiseSvn?
(I downloaded it form <http://tortoisesvn.net/downloads.html>
http://tortoisesvn.net/downloads.html, for 32-bit OS)
I appreciate your help.
Thanks,
Carmit
Re: problem with dialog box uisng Tortoisesvn
Posted by Carmit Shiran <ca...@gmail.com>.
On Wed, Sep 5, 2012 at 11:43 AM, Cooke, Mark <ma...@siemens.com> wrote:
> > -----Original Message-----
> > From: Carmit Shiran [mailto:carmit.shiran@gmail.com]
> > Sent: 05 September 2012 09:25
> > To: users@subversion.apache.org
> > Subject: problem with dialog box uisng Tortoisesvn
> >
> > hello,
> > I downloaded Tortoisesvn to my computer.
> > I want the following command to be executed without opening
> > the dialog box at the end (I don't want the user to enter any data):
> >
> > TortoiseProc.exe /command:commit
> > /path:"C:\Projects\Widget3_Dev" /closeonend:1
> >
> > The /closeonend:1 doesn't seem to work. I still get the pop-up dialog.
> >
> > I also tried changing the settings and switched the:
> > General->Dialogs 1-> Autoclose to : Auto-close if no errors.
> >
> > But this also doesn't work.
> >
> > Can you help me out?
> > What am I not doing right?
> >
> > Thanks,
> > Carmit
>
> Why not just use the svn command line tools (they are an optional
> component when you install TortoiseSVN)? You could then call `svn commit`,
> see the on-line book help:-
>
>
> http://svnbook.red-bean.com/en/1.7/svn.tour.cycle.html#svn.tour.cycle.commit
>
> ~ mark c
>
OK- I tired now:
c:\Program files\TortoiseSVN\bin> $svn commit
I got the following message:
'$svn' is not recognized as an internal or external command, operable
program or batch file.
Where exaclty am I supposed to write this command. I dont' see in the
book....
In what path on the cmd line? Is this how to use it?
Do I write $svn? or just svn (which also didn;t work for me)?
Am I supposed to download anything else besides TortoiseSvn?
(I downloaded it form http://tortoisesvn.net/downloads.html, for 32-bit OS)
I appreciate your help.
Thanks,
Carmit
RE: problem with dialog box uisng Tortoisesvn
Posted by "Cooke, Mark" <ma...@siemens.com>.
> -----Original Message-----
> From: Carmit Shiran [mailto:carmit.shiran@gmail.com]
> Sent: 05 September 2012 09:25
> To: users@subversion.apache.org
> Subject: problem with dialog box uisng Tortoisesvn
>
> hello,
> I downloaded Tortoisesvn to my computer.
> I want the following command to be executed without opening
> the dialog box at the end (I don't want the user to enter any data):
>
> TortoiseProc.exe /command:commit
> /path:"C:\Projects\Widget3_Dev" /closeonend:1
>
> The /closeonend:1 doesn't seem to work. I still get the pop-up dialog.
>
> I also tried changing the settings and switched the:
> General->Dialogs 1-> Autoclose to : Auto-close if no errors.
>
> But this also doesn't work.
>
> Can you help me out?
> What am I not doing right?
>
> Thanks,
> Carmit
Why not just use the svn command line tools (they are an optional component when you install TortoiseSVN)? You could then call `svn commit`, see the on-line book help:-
http://svnbook.red-bean.com/en/1.7/svn.tour.cycle.html#svn.tour.cycle.commit
~ mark c
Re: problem with dialog box uisng Tortoisesvn
Posted by Thorsten Schöning <ts...@am-soft.de>.
Guten Tag Carmit Shiran,
am Mittwoch, 5. September 2012 um 10:24 schrieben Sie:
> What am I not doing right?
You are at least on the wrong mailing list, Tortoise has its own.
http://tortoisesvn.net/support.html
Mit freundlichen Grüßen,
Thorsten Schöning
--
Thorsten Schöning E-Mail:Thorsten.Schoening@AM-SoFT.de
AM-SoFT IT-Systeme http://www.AM-SoFT.de/
Telefon.............030-2 1001-310
Fax...............05151- 9468- 88
Mobil..............0178-8 9468- 04
AM-SoFT GmbH IT-Systeme, Brandenburger Str. 7c, 31789 Hameln
AG Hannover HRB 207 694 - Geschäftsführer: Andreas Muchow