RE: WIP branches

e I opened a MR for this wip/ branch, and if so which MR?". There really should be a way to answer that question. Simon | -Original Message- | From: ghc-devs On Behalf Of Ben Gamari | Sent: 06 February 2019 22:34 | To: Matthew Pickering ; Sylvain Henry | | Cc: ghc-devs | Subje

Re: WIP branches

Matthew Pickering writes: > Making `ghc-wip` sounds like a reasonable idea to me. > > I have found that people pushing to the `wip/` branches makes things > much smoother so far as it means that I can rebase/finish/amend other > people's patches and just push to the same branch

Re: WIP branches

Making `ghc-wip` sounds like a reasonable idea to me. I have found that people pushing to the `wip/` branches makes things much smoother so far as it means that I can rebase/finish/amend other people's patches and just push to the same branch without having to ask people to do annoying rebases

Re: WIP branches

evs just have their > own forks? > > > > Thanks, > > Richard > > > >> On Feb 5, 2019, at 11:36 AM, Sylvain Henry wrote: > >> > >> Hi, > >> > >> Every time we fetch the main GHC repository, we get *a lot* of "wip/*" > branches.

Re: WIP branches

*a lot* of "wip/*" branches. That's a lot of noise, making the bash completion of "git checkout" pretty useless for instance: git checkout zsh: do you wish to see all 945 possibilities (329 lines)? Unless I'm missing something, they seem to be used to: 1) get the CI run on pe

WIP branches

Hi, Every time we fetch the main GHC repository, we get *a lot* of "wip/*" branches. That's a lot of noise, making the bash completion of "git checkout" pretty useless for instance: > git checkout zsh: do you wish to see all 945 possibilities (329 lines)? Unles

Re: Non-wip/* branches

Joachim Breitner writes: > Hi, > >> facundominguez added a comment. >>  >> @nomeata please, could you remove the branches fd/fix-travis and  >> fd/fix-travis2? Some server hook is preventing me from doing so. > > turns out I cannot do that either (which I knew). From

Re: Commit messages for WIP branches (Was: Question about `validate` workflow)

to `wip/*` branches. What do we think? of course it is nice to know what others are working on, and someone interested in your particular thing might have a look. But especially due to rebasing the current commit message setup does not work for wip branches. We could experimenting with just

Re: Commit messages for WIP branches (Was: Question about `validate` workflow)

On Nov 10, 2014, at 3:33 AM, Joachim Breitner m...@joachim-breitner.de wrote: We could experimenting with just sending those „branch wip/foo's head updated“ mails, i.e. only one mail per push, listing the git commit titles. That would greatly reduce the traffic, while still giving some

Commit messages for WIP branches (Was: Question about `validate` workflow)

slightly embarrassed when I push to my `wip/rae` branch, causing other people to get emails about my internal GHC meanderings. But, I'm using GHC's repo now for better integration with Phab, for when Harbormaster pulls base commits. So, I propose: Do not send commit emails for commits to `wip