On Tue, Jan 14, 2020 at 12:35:27PM +0800, Ben Coman wrote:
> Even from the command line I find slashes in branch names problematic,
> because slashes are as a "remote/branch" separator incites confusion about
> what is being referenced.
>
> Other have different problems...
The VM's shell scripts
Ben Coman wrote
> I find slashes in branch names problematic
Okay, you've convinced me. How do we guide people toward that policy? A
warning when creating such branches? At minimum we should change the ghost
text from Iceberg's branch creation dialog, which suggests "feature/what" as
a branch temp
There is a new Pharo build available!
The status of the build #6 was: SUCCESS.
The Pull Request #5455 was integrated: "Made metalinks installable on ast nodes
by selecting code when browsing methods in Calypso"
Pull request url: https://github.com/pharo-project/pharo/pull/5455
Issue Url: http
There is a new Pharo build available!
The status of the build #1106 was: FAILURE.
The Pull Request #5484 was integrated:
"5481-Metacello-logs-now-prints-lots-of-new-lines"
Pull request url: https://github.com/pharo-project/pharo/pull/5484
Issue Url: https://github.com/pharo-project/pharo/issu
On Tue, 14 Jan 2020 at 21:26, Sean P. DeNigris wrote:
>
> Ben Coman wrote
> > I find slashes in branch names problematic
>
> Okay, you've convinced me. How do we guide people toward that policy?
> A warning when creating such branches?
That sounds reasonable. Perhaps a discrete warning icon/butto
