Re: Problem with svndumpfilter
Another option is to use Subdivision, a commercial tool that is
designed to do exactly these kinds of operations, in other works
Delete files, Extract files, Split repositories in two parts.
Subdivision reads the repository structure in memory and 'understands'
the structure of your repository. It can therefore create the
necessary derived selections from your selections to make sure that
the delete operation succeeds in the first pass. In this example,
Subdivision would make sure that /branches/develop/dir2 would be
available for the copy to be made from it (or that both source and
copy would both be unavailable - depending on the user selections).
Subdivision is a Windows application but we are working on a Linux
solution too. You can try a demo by visiting http://subdi.vision
Goes without saying that we are affiliated with Subdivision and we are
sorry for the shameless advertising but we believe people in this
group will benefit from knowing that Subdivision exists.
On Thu, Jun 7, 2018 at 6:08 PM Stefan Sperling wrote:
>
> On Thu, Jun 07, 2018 at 10:40:51AM -0400, Alfred von Campe wrote:
> > Thanks, Stefan. The path of least resistance for me is to use the script
> > you pointed me to. However, it seems that the exclude feature is not yet
> > implemented:
> >
> > try:
> > if args[0] == 'include':
> > sys.exit(analyze_logs(map(sanitize_path, targets)))
> > elif args[0] == 'exclude':
> > usage_and_exit("Feature not implemented")
> > else:
> > usage_and_exit("Valid subcommands are 'include' and 'exclude'")
> >
> > Is there a more recent version of this script?
>
> I am afraid not. The link I provided points to the latest version of
> this script we have in our repository. We would welcome patches to
> the script. However, since the problem has been fixed in SVN 1.10's
> version of 'svnadmin' I think it makes more sense to just use 1.10.
>
> You could install 1.10 binaries somewhere next to your existing SVN
> installation and use the 1.10 svnadmin binary to create a dump file.
> The resulting dump file will be compatible with older versions.
Re: Problem with svndumpfilter
On 08.06.2018 10:20, Doros Agathangelou wrote:
> Another option is to use Subdivision, a commercial tool that is
> designed to do exactly these kinds of operations, in other works
> Delete files, Extract files, Split repositories in two parts.
> Subdivision reads the repository structure in memory and 'understands'
> the structure of your repository. It can therefore create the
> necessary derived selections from your selections to make sure that
> the delete operation succeeds in the first pass. In this example,
> Subdivision would make sure that /branches/develop/dir2 would be
> available for the copy to be made from it (or that both source and
> copy would both be unavailable - depending on the user selections).
>
> Subdivision is a Windows application but we are working on a Linux
> solution too. You can try a demo by visiting http://subdi.vision
>
> Goes without saying that we are affiliated with Subdivision and we are
> sorry for the shameless advertising but we believe people in this
> group will benefit from knowing that Subdivision exists.
Before advertising proprietary, platform-specific tools, I'd first
suggest that the OP take a look at
https://gitlab.com/esr/reposurgeon
which also supports these kinds of operations and is open source.
> On Thu, Jun 7, 2018 at 6:08 PM Stefan Sperling wrote:
>> On Thu, Jun 07, 2018 at 10:40:51AM -0400, Alfred von Campe wrote:
>>> Thanks, Stefan. The path of least resistance for me is to use the script
>>> you pointed me to. However, it seems that the exclude feature is not yet
>>> implemented:
>>>
>>> try:
>>> if args[0] == 'include':
>>> sys.exit(analyze_logs(map(sanitize_path, targets)))
>>> elif args[0] == 'exclude':
>>> usage_and_exit("Feature not implemented")
>>> else:
>>> usage_and_exit("Valid subcommands are 'include' and 'exclude'")
>>>
>>> Is there a more recent version of this script?
>> I am afraid not. The link I provided points to the latest version of
>> this script we have in our repository. We would welcome patches to
>> the script. However, since the problem has been fixed in SVN 1.10's
>> version of 'svnadmin' I think it makes more sense to just use 1.10.
>>
>> You could install 1.10 binaries somewhere next to your existing SVN
>> installation and use the 1.10 svnadmin binary to create a dump file.
>> The resulting dump file will be compatible with older versions.
Problem setting Notepad++ as log message editor for svn 1.9.7 (Windows7)
I have configured Notepad++ to be the editor for the log message. This works OK if Notepad++ is *not* running at the time of an svn operation. Then Npp pops up an edit window and I can enter the message as expected and then close the window. But when Npp is already running with one or several tabs with other file edits, then Npp pops up with an edit tab inside the already running window. Now svn will not recognize my log message but instead pop up the following on the command line: Log message unchanged or not specified (a)bort, (c)ontinue, (e)dit: If I choose c then the commit proceeds but there is no log message... How can I use Notepad++ as the log editor and not have this happening? -- Bo Berglund Developer in Sweden
Re: Problem setting Notepad++ as log message editor for svn 1.9.7 (Windows7)
Bo Berglund wrote on Fri, 08 Jun 2018 18:29 +0200: > How can I use Notepad++ as the log editor and not have this happening? Subversion runs the editor command with system() and expects that when system() returns, if the exit code is zero then the user has finished editing the log message. You should ask the Notepad++ guys how to invoke it in a way that satisfies this contract. There may be a command-line flag you can pass (e.g., I use editor-cmd='gvim -f'). Cheers, Daniel
Re: Problem setting Notepad++ as log message editor for svn 1.9.7 (Windows7)
On Fri, Jun 8, 2018 at 12:41 PM Daniel Shahaf wrote: > Bo Berglund wrote on Fri, 08 Jun 2018 18:29 +0200: > > How can I use Notepad++ as the log editor and not have this happening? > > Subversion runs the editor command with system() and expects that when > system() returns, if the exit code is zero then the user has finished > editing the log message. You should ask the Notepad++ guys how to > invoke it in a way that satisfies this contract. There may be a > command-line > flag you can pass (e.g., I use editor-cmd='gvim -f'). Or write a wrapper around it? >
Re: Problem setting Notepad++ as log message editor for svn 1.9.7 (Windows7)
On Fri, Jun 8, 2018 at 12:29 PM, Bo Berglund wrote: > I have configured Notepad++ to be the editor for the log message. > This works OK if Notepad++ is *not* running at the time of an svn > operation. Then Npp pops up an edit window and I can enter the message > as expected and then close the window. > > But when Npp is already running with one or several tabs with other > file edits, then Npp pops up with an edit tab inside the already > running window. > Now svn will not recognize my log message but instead pop up the > following on the command line: > > Log message unchanged or not specified > (a)bort, (c)ontinue, (e)dit: > > If I choose c then the commit proceeds but there is no log message... > > How can I use Notepad++ as the log editor and not have this happening? > > See: http://notes.richdougherty.com/2012/05/using-notepad-to-edit-subversion-commit.html You need to add the -multiInst option. The full set of options you should add actually seems to be: -multiInst -noPlugin -nosession -notabbar -- Thanks Mark Phippard http://markphip.blogspot.com/
Re: Problem setting Notepad++ as log message editor for svn 1.9.7 (Windows7)
On Fri, 8 Jun 2018 14:57:06 -0400, Mark Phippard wrote: >On Fri, Jun 8, 2018 at 12:29 PM, Bo Berglund wrote: > >> I have configured Notepad++ to be the editor for the log message. >> This works OK if Notepad++ is *not* running at the time of an svn >> operation. Then Npp pops up an edit window and I can enter the message >> as expected and then close the window. >> >> But when Npp is already running with one or several tabs with other >> file edits, then Npp pops up with an edit tab inside the already >> running window. >> Now svn will not recognize my log message but instead pop up the >> following on the command line: >> >> Log message unchanged or not specified >> (a)bort, (c)ontinue, (e)dit: >> >> If I choose c then the commit proceeds but there is no log message... >> >> How can I use Notepad++ as the log editor and not have this happening? >> >> > >See: >http://notes.richdougherty.com/2012/05/using-notepad-to-edit-subversion-commit.html > >You need to add the -multiInst option. > >The full set of options you should add actually seems to be: -multiInst >-noPlugin -nosession -notabbar Thanks, I added the -multiInst option to make the config file line read: editor-cmd = "C:\Programs\Notepad++\notepad++.exe -multiInst" And now it seems to work at least for my use case even though I did not throw in the other switches. Thanks for your help! -- Bo Berglund Developer in Sweden
