On Thu, Nov 28, 2019 at 8:51 PM Daniel Shahaf
wrote:
> Nathan Hartman wrote on Fri, 29 Nov 2019 01:41 +00:00:
> > On Thu, Nov 28, 2019 at 4:18 PM Daniel Shahaf
> wrote:
> > > Is -prune portable? I don't see it in the POSIX spec of find(1).
> >
> > Where did you look? This page mentions -prune a
Nathan Hartman wrote on Fri, 29 Nov 2019 01:41 +00:00:
> On Thu, Nov 28, 2019 at 4:18 PM Daniel Shahaf wrote:
> > Is -prune portable? I don't see it in the POSIX spec of find(1).
>
> Where did you look? This page mentions -prune and even provides an example:
> https://pubs.opengroup.org/onlinepu
On Thu, Nov 28, 2019 at 4:18 PM Daniel Shahaf
wrote:
> Yasuhito FUTATSUKI wrote on Fri, Nov 29, 2019 at 00:15:48 +0900:
> > Hi, while I do 'make distclean', I find odd `find' usage.
> >
> > In Makefile.in:
> > > gcov-clean:
> > > rm -f gcov-lcov.dat gcov-lcov.log gcov-genhtml.log
> > > rm
Branko Čibej wrote on Thu, 28 Nov 2019 21:30 +00:00:
> I think this warrants a bug report to infra because the link really
> should work correctly.
Created https://issues.apache.org/jira/browse/INFRA-19500.
Thanks,
Daniel
On 28.11.2019 22:17, Daniel Shahaf wrote:
> That used to be documented
> on http://wiki.apache.org/subversion/BuildNotes, but I'm not sure if that
> link's
> still valid — it just gives me a login prompt now ☹)
It's a broken redirect to Confluence and I don't know why it's not
globally readable,
Yasuhito FUTATSUKI wrote on Fri, Nov 29, 2019 at 00:15:48 +0900:
> Hi, while I do 'make distclean', I find odd `find' usage.
>
> In Makefile.in:
> > gcov-clean:
> > rm -f gcov-lcov.dat gcov-lcov.log gcov-genhtml.log
> > rm -rf gcov-report
> > find . -name "*.gcda" -o -name "*.gcno" -ex
Yasuhito FUTATSUKI wrote on Thu, Nov 28, 2019 at 20:36:25 +0900:
> And there seems to be also some scripts calling Python
> interpreter with -c option.
>
> I roughly searched:
> [[[
> $ find . -name .svn -prune -or -type f -print0 | xargs -0 egrep -i
> '(^|[^-])python.* -c'
I suggest to also gre
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
>
Hi, while I do 'make distclean', I find odd `find' usage.
In Makefile.in:
gcov-clean:
rm -f gcov-lcov.dat gcov-lcov.log gcov-genhtml.log
rm -rf gcov-report
find . -name "*.gcda" -o -name "*.gcno" -exec rm -f -- {} \;
Is it intended below ?
find . \( -name "*.gcda"
On Thu, Nov 28, 2019 at 5:11 AM Lukas .. wrote:
> ---
> Subversion Exception!
> ---
> Subversion encountered a serious problem.
> Please take the time to report this on the Subversion mailing list
> with as much information as possible about what
>
On 28.11.2019 02:54, Nathan Hartman wrote:
> contrib/client-side/svnmerge/svnmerge-migrate-history.py
> contrib/client-side/svnmerge/svnmerge_test.py
> contrib/client-side/svnmerge/svnmerge.py
> contrib/client-side/svnmerge/svnmerge-migrate-history-remotely.py
I think we should move 'svnmerge' t
On 2019/11/28 10:54, Nathan Hartman wrote:
FYI I have made a list of all our Python scripts, categorized in a
very *preliminary* manner into one of three categories:
* Python 3 supported
* Python 3 not supported yet
* Not checked yet
It is preliminary because I've based my categorization on rece
---
Subversion Exception!
---
Subversion encountered a serious problem.
Please take the time to report this on the Subversion mailing list
with as much information as possible about what
you were trying to do.
But please first search the mailing list
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
15 matches
Mail list logo
