Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Upgrade Subversion #374

Closed
dscho opened this issue Sep 10, 2015 · 6 comments
Closed

Upgrade Subversion #374

dscho opened this issue Sep 10, 2015 · 6 comments

Comments

@dscho
Copy link
Member

dscho commented Sep 10, 2015

We are shipping with Subversion 1.8.13 bindings right now, but 1.9.1 is out.

@dscho
Copy link
Member Author

dscho commented Sep 10, 2015

Current progress: git-for-windows/MSYS2-packages@master...dscho:subversion

The main problem is apr right now: its test suite is failing because it is configured without threads.

@dscho
Copy link
Member Author

dscho commented Sep 10, 2015

Oh yeah, mustn't forget: the main reason why I want to rebuild apr is because apr-1-config --link-libtool prints options including -R /usr/lib/ which is readily ingested into serf's /usr/lib/pkgconfig/serf-1.pc -- which is incorrect because while libtool can grok the -R option, GCC's linker cannot.

@nalla
Copy link

nalla commented Sep 14, 2015

@dscho
Copy link
Member Author

dscho commented Sep 14, 2015

Indeed! I just saw it...

@dscho dscho closed this as completed Sep 14, 2015
@nalla
Copy link

nalla commented Sep 14, 2015

I did a (64bit)

/usr/bin/time prove -j 5 --state=failed,save ./t91*.sh

against 0c51399. Seems to introduce no side effects.

@dscho
Copy link
Member Author

dscho commented Sep 14, 2015

Thanks for confirming!

jeffhostetler pushed a commit to jeffhostetler/git that referenced this issue Jul 2, 2021
Replaces git-for-windows#367, which used the upstream commits directly. This instead includes a merge commit onto `vfs-2.32.0` so we can move forward even if the upstream version is modified.

This integrates the sparse-index with `git status`. There is a LOT of code here, and much of it makes future changes (git-for-windows#361 and git-for-windows#364) much simpler than they would be otherwise.

This merges into `features/sparse-index` which is intended to be released as an experimental release. The goal of reviewing this PR is to find "good enough for a limited release to dogfooders" and not the same scrutiny of upstream.

In particular, I am currently looking for an issue with directory/file conflicts at the sparse-checkout boundary. They don't reveal themselves until `git checkout`, and only in very rare cases that won't affect our dogfooders.
jeffhostetler pushed a commit to jeffhostetler/git that referenced this issue Jul 2, 2021
…nd `git checkout`

See gitgitgadget#973 for the upstream submission.

This PR follows git-for-windows#374 which does the heavy lifting.

There is one known issue with this integration: directory/file conflicts at the sparse-checkout boundary. This will not affect our dogfooders so we should ignore that bug for the purpose of the `features/sparse-index` branch. I will fix that upstream.
jeffhostetler pushed a commit to jeffhostetler/git that referenced this issue Jul 2, 2021
…se-index

This follows git-for-windows#374 and git-for-windows#361 to complete the necessary functionality for the sparse-index experimental release.

This does not include the behavior changes requested upstream. The request is about how `git add` currently ignores changes that match a tracked path outside of the sparse-checkout definition. However, this is an established behavior of Git, so we don't need to change it for our dogfooders.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants