Menu
Learn
Documentation
Language Reference
Library Reference
Command-line Reference
Feature Overview
Articles
Downloads
Packages
Community
Blog
Orgs using D
Twitter
Calendar
Forums
IRC
Wiki
GitHub
Issues
Get involved
Contributors
Foundation
Donate
Sponsors
Resources
Tour
Books
Tutorials
Tools
Editors
IDEs
Visual D
Acknowledgments
D Style
Glossary
Sitemap
Search
Entire Site
Language
Library
Forums
Learn group
This thread
go
Forums
Forum Index
New users
Learn
Community
General
Announce
Improvements
DIP Ideas
DIP Devel.
Ecosystem
GDC
LDC
Debuggers
IDEs
DWT
Development
Internals
Issues
Beta
DMD
Phobos
Druntime
Study
Turkish
Genel
Duyuru
Log in
Settings
Help
Index
»
Learn
»
github: What to do when unittests fail?
»
Post reply
Warning: the post you are replying to is from 14 years ago (May 24, 2011).
Posting to
Learn
in reply to
Andrej Mitrovic
Your name:
Your email address (
?
):
Subject:
Message:
On Tuesday, 24 May 2011 at 13:01:59 UTC, Andrej Mitrovic wrote: > On 5/24/11, David Nadlinger <see@klickverbot.at> wrote: >> master, then create a feature branch for your pull request >> (»git >> checkout -b spiffy-new-feature«). > > Ok, but what about the errors in my original post? I should > make sure all unittests pass when I make a pull request, right? > > If that's required I think I'd have to first checkout an older > commit. But I'm not sure which one. There's a bunch of them for > dates May 16th and older listed here: > http://d.puremagic.com/test-results/platform-history.ghtml?os=Win_32 > > E.g. this one: > http://d.puremagic.com/test-results/test_data.ghtml?dataid=62436 It says: >>From git://github.com/D-Programming-Language/phobos > 3b628ae..d1d8124 master -> origin/master > > I'm not sure what 3b628ae..d1d8124 means, should I do "git > checkout d1d8124" or something similar to get this commit?
Enable
Markdown
Copyright © 1999-2021 by the
D Language Foundation
