-
Notifications
You must be signed in to change notification settings - Fork 106
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
Added contents_first option #19
Conversation
Added ability to yield the contents of the directory before the directory itself
Thanks for doing this! I've only glanced at it, but it seems reasonable. I will need to do a more thorough review before merging though. From skimming, I see that the code style is pretty inconsistent. Can you please write code in a style that is consistent with the rest of the code in this repo? As it stands now, I see a lot of indentation inconsistencies. Please also adhere to a 79 column limit (inclusive). |
Sure will do. Just realised that I forgot to get approval from our open
source folks (should just a formality) so please don't submit yet...
On 2 Feb 2017 5:19 pm, "Andrew Gallant" <notifications@github.com> wrote:
Thanks for doing this! I've only glanced at it, but it seems reasonable. I
will need to do a more thorough review before merging though.
From skimming, I see that the code style is pretty inconsistent. Can you
please write code in a style that is consistent with the rest of the code
in this repo? As it stands now, I see a lot of indentation inconsistencies.
Please also adhere to a 79 column limit (inclusive).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#19 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ALbIF_p8vwi6HGLuSOuaqqcXSgYIUv6iks5rYhABgaJpZM4L1WtK>
.
|
Right I think I've updated the pull request with a format change commit. Apologies for that - hadn't realised that my eclipse setup was set to use tabs under some circumstances. Also have permission to submit the code now, the powers that be have checked that I'm not giving away confidential google code :-) |
Go for it @mcharsley. I ended up not needing a post-order option in my project, so my branch is neglected... |
@BurntSushi : friendly ping now Michael's bowed out... |
@mcharsley All set! Sorry for the delay. Thanks so much! |
Excellent, thanks very much.
Have you got an ETA for a release to crates.io with this in?
In the meantime I'll change my cargo file to point to the official github
project rather than my fork :-)
Mark
…On Tue, May 9, 2017 at 12:04 AM, Andrew Gallant ***@***.***> wrote:
@mcharsley <https://github.com/mcharsley> All set! Sorry for the delay.
Thanks so much!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#19 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ALbIF619vC3CPD1MXOcPrRXMQnTti8shks5r359qgaJpZM4L1WtK>
.
|
#18
Added ability to yield the contents of the directory before the
directory itself