An idea for improving workflow

[Jan Stolarek]

Daniel,

this is a nice idea, but it does not address the issue I am mentioning. The problem is that GHC an 
testsuite are two diferent repositories. One might commit changes to both of them, but if only 
one repo is pushed to the central git server, the problem with failing validation might occur. 
Also, every developer would have to set this up on her own, whereas my proposal is set up on the 
central server and automatically affects everyone pushing to the repo.

Janek

Dnia poniedziałek, 25 marca 2013, Daniel Trstenjak napisał:
> Hi Jan,
>
> On Mon, Mar 25, 2013 at 03:36:38PM +0100, Jan Stolarek wrote:
> > I've been reading the ghc-devs list for quite some time now and I noticed
> > that it often happens that one of the developers pushes the changes to
> > the ghc.git repo but forgets to push the corresponding changes to the
> > testsuite, which results in people trying to figure out why their
> > validation fails.
>
> I quite like having the shell prompt indicating if there're uncommited
> changes.
>
> A "clean" repo just displays the branch name:
> dan at machine ~/.../somePath [BranchName]>
>
> With uncommited changes:
> dan at machine ~/.../somePath [BranchName *]>
>
> Something stashed:
> dan at machine ~/.../somePath [BranchName $]>
>
> Untracked files:
> dan at machine ~/.../somePath [BranchName %]>
>
>
> The prompt relevant settings for the bash shell (.bashrc) are:
>
> # which kind of state should be displayed
> export GIT_PS1_SHOWDIRTYSTATE=1
> export GIT_PS1_SHOWSTASHSTATE=1
> export GIT_PS1_SHOWUNTRACKEDFILES=1
>
> # the prompt
> export PS1='\u@\h \w$(__git_ps1 " [%s]")> '
>
>
> The git relevant part of the prompt is: $(__git_ps1 " [%s]")
>
>
> Greetings,
> Daniel
>
> _______________________________________________
> ghc-devs mailing list
> ghc-devs at haskell.org
> http://www.haskell.org/mailman/listinfo/ghc-devs