Re: mtimes of working files

From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
Date: Jul 14, 2007, 13:23 UTC
Message-ID: <200707141523.32929.robin.rosenberg.lists@dewire.com>
In-Reply-To: <1184374174.2785.104.camel@shinybook.infradead.org>

lördag 14 juli 2007 skrev David Woodhouse:

Show 13 quoted lines

> On Fri, 2007-07-13 at 20:44 -0400, J. Bruce Fields wrote:
> > On Sat, Jul 14, 2007 at 01:36:33AM +0100, David Woodhouse wrote:
> > > Yeah, much of it. Although I've also seen other people trying to get
> > > to grips with git and tripping up over branches recently.
> > 
> > Could you give any details?  What specifically was it they were having
> > trouble with? 
> 
> Just conversations on IRC where stuff had to be explained. People not
> understanding that they'd actually cloned _multiple_ branches and they
> needed to select the one they wanted, making the same kind of stupid
> mistakes I did with committing to the wrong place, etc. Nothing specific
> stands out as being fixable, certainly.

That's why there are scripts that modify the bash prompt to show the current branch. I made one for stacked git (it works with plain git too). The git completion scripts have something also I think

It helps a lot for those of us with bad memory implants.

> Branches have their place, and some people seem very happy with them as
> part of their local workflow. I just wonder if we have to have them on
> the servers too; that's all.

Branches are bad if you don't need them as is any feature you don't need is bad, it is just that many people need branches. Branches are a pain to manage with many SCM tools, except git, which solves most of the problems with branches.

-- robin