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

CTRL-C event kills the application #203

Closed
wants to merge 1 commit into from

Conversation

cbucher
Copy link

@cbucher cbucher commented Jun 17, 2015

All events are disabled!
The only way to exit this program is the launched command end.

All events are disabled!
The only way to exit this program is the launched command end.
@bviktor
Copy link

bviktor commented Jun 17, 2015

Related: #96

@dscho
Copy link
Member

dscho commented Jun 17, 2015

@cbucher thanks!

I would like to ask you to improve the commit message, though:

@dscho
Copy link
Member

dscho commented Jun 18, 2015

@cbucher please just force-push to update the Pull Request in the future instead of opening a separate Pull Request for subsequent iterations.

Continuing discussion here: #205

@dscho dscho closed this Jun 18, 2015
jeffhostetler pushed a commit to jeffhostetler/git that referenced this pull request Oct 7, 2019
If a user provides folders A/ and A/B/ for inclusion in a cone-mode
sparse-checkout file, the parsing logic will notice that A/ appears
both as a "parent" type pattern and as a "recursive" type pattern.
This is unexpected and hence will complain via a warning and revert
to the old logic for checking sparse-checkout patterns.

Prevent this from happening accidentally by sanitizing the folders
for this type of inclusion in the 'git sparse-checkout' builtin.
This happens in two ways:

1. Do not include any parent patterns that also appear as recursive
   patterns.

2. Do not include any recursive patterns deeper than other recursive
   patterns.

**Note:** The old behavior surfaces as a performance issue, not a
correctness issue. The test checks the expected data in the
sparse-checkout file to ensure it is behaving as expected.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants