Re: Fwd: error while running make check (g++ 4.7.0): missing include of unistd.h

[David Kastrup]

Frédéric Bron <address@hidden> writes:

>> A description of the issue.  For new issues, this is usually filled in
>> with the commit message(s) automatically.
>
> OK, I did it but failed when asking for :
> Could not find stored credentials
>   /home/fred/.lilypond-project-hosting-login
> Please enter login details manually
> Username (google account name):
>
> I entered my first name + surname instead of google login so then I
> Ctrl+C. I do not know if it worked (created issue
> http://codereview.appspot.com/6434048).
>
> Now, I want to send a patch for already existing issues (2401 and
> 2563). Is there a link between codereview issue numbers and tracker
> issue numbers?

No.  Our tools establish that link by looking at the last comment on an
issue that has a codereview URL.

> Should I create new codereview issues for these?

Yes.  Independent patches need independent codereviews.  If your commit
message starts with "Issue 2401:" then git-cl will usually pick that up
as a suggestion for the issue number to use, and it will also make it
easier to find the issue in the tracker if people encounter it in the
commit history.

-- 
David Kastrup