This page is no longer maintained — Please continue to the home page at www.scala-lang.org

Fwd: Re: [scala-devel] Github workflow - continue working on an issue that's already been pulled in

No replies
prokopec
Joined: 2010-02-19,
User offline. Last seen 34 weeks 5 days ago.
Moved to internals.

-------- Original Message -------- Subject: Re: [scala-devel] Github workflow - continue working on an issue that's already been pulled in Date: Wed, 25 Jan 2012 07:42:19 -0800 From: Paul Phillips paulp [at] improving [dot] org (<paulp [at] improving [dot] org>) Reply-To: scala-devel [at] epfl [dot] ch (<scala-devel [at] epfl [dot] ch>) To: scala-devel [at] epfl [dot] ch (<scala-devel [at] epfl [dot] ch>)



On Wed, Jan 25, 2012 at 7:07 AM, Aleksandar Prokopec <aleksandar [dot] prokopec [at] epfl [dot] ch" rel="nofollow">aleksandar [dot] prokopec [at] epfl [dot] ch> wrote:
Does anyone know what our policy is for continuing to work on an issue that's already been pulled in to scala/scala?
Should I:
1) start a new branch to refine what I did before on issue/XXXX? In this  case, what is the naming convention?
2) or continue working on the old  branch issue/XXXX (previously pulled to scala/scala) and just send the pull request again once I'm happy with my changes?

Either of these is fine I think.
(Also, I should echo the feeling of others we should send these questions to -internals.)

Copyright © 2012 École Polytechnique Fédérale de Lausanne (EPFL), Lausanne, Switzerland