Of course.
On 02.12.2019 12:12, Paul Hammant wrote:
> All of which can be played out in the issues and the PRs of the most
> viable GitHub repo for this idea.
At some point you're going to have to come back and discuss any design
on this list.
-- Brane
All of which can be played out in the issues and the PRs of the most viable
GitHub repo for this idea.
On 02.12.2019 11:48, Paul Hammant wrote:
> > ... "pointing at GitHub not going to solve anything" ...
>
> I was pointing at a GitHub repo in order for the OP to use that, and
> perhaps contribute to it there. It can easily be perfected there in
> (say) Python, and in a couple of years time re-imple
> ... "pointing at GitHub not going to solve anything" ...
I was pointing at a GitHub repo in order for the OP to use that, and
perhaps contribute to it there. It can easily be perfected there in (say)
Python, and in a couple of years time re-implemened in C in for Svn on
Apache's canonical Svn 'u
On 02.12.2019 10:56, Paul Hammant wrote:
> This is a fantastic feature. At least, it is very popular in Git and
> Mercurial.
>
> In lieu of the Svn dev team agreeing, there's at least two
> implementations on GitHub - https://github.com/search?q=subversion+ignore
Clearly there's interest for havi
This is a fantastic feature. At least, it is very popular in Git and
Mercurial.
In lieu of the Svn dev team agreeing, there's at least two implementations
on GitHub - https://github.com/search?q=subversion+ignore
On Fri, Nov 29, 2019 at 11:12 AM Krzysztof Siewiorek
wrote:
> Hi,
> Thank you all
Hi, Thank you all for the feedback. You are right. I was not too precise on
what is the problem, and what is used already. We are using the latest version
of Subversion (1.13.0), and the latest TortoiseSVN client (1.13.1), so we take
advantage of svn:global-ignores properties - and that featur
On Thu, Nov 28, 2019 at 2:20 AM Krzysztof Siewiorek
wrote:
> Hi!
> We've started to move from Perforce to SVN in my company for some reasons.
> We moved quite a few big projects that we have or we had been working in
> the past. Working with perforce for years gave us quite a big and precise
> ig
On Wed, Nov 27, 2019 at 12:25:06PM +0100, Krzysztof Siewiorek wrote:
> Hi! We've started to move from Perforce to SVN in my company for some
> reasons. We moved quite a few big projects that we have or we had been
> working in the past. Working with perforce for years gave us quite a big and
>
On 27.11.2019 12:25, Krzysztof Siewiorek wrote:
> Hi!
> We've started to move from Perforce to SVN in my company for some
> reasons. We moved quite a few big projects that we have or we had been
> working in the past. Working with perforce for years gave us quite a
> big and precise ignore rules li
Hi! We've started to move from Perforce to SVN in my company for some
reasons. We moved quite a few big projects that we have or we had been working
in the past. Working with perforce for years gave us quite a big and precise
ignore rules list. The problem is that SVN's approach to that does no
12 matches
Mail list logo