From: Robin Rosenberg <robin.rosenberg.lists@dewire.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Theodore Tso <tytso@mit.edu>,
Andy Parkins <andyparkins@gmail.com>,
git@vger.kernel.org, Jan Hudec <bulb@ucw.cz>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: mtimes of working files
Date: Sat, 14 Jul 2007 15:23:32 +0200 [thread overview]
Message-ID: <200707141523.32929.robin.rosenberg.lists@dewire.com> (raw)
In-Reply-To: <1184374174.2785.104.camel@shinybook.infradead.org>
lördag 14 juli 2007 skrev David Woodhouse:
> 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
next prev parent reply other threads:[~2007-07-14 13:22 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 15:08 mtimes of working files Yakov Lerner
2007-07-11 18:05 ` Johannes Schindelin
2007-07-11 18:36 ` Yakov Lerner
2007-07-11 18:42 ` Johannes Schindelin
2007-07-11 20:26 ` Jan Hudec
2007-07-12 7:57 ` Andy Parkins
2007-07-12 17:27 ` David Woodhouse
2007-07-13 0:37 ` Theodore Tso
2007-07-13 23:00 ` David Woodhouse
2007-07-13 23:18 ` Linus Torvalds
2007-07-13 23:46 ` David Woodhouse
2007-07-14 0:10 ` Linus Torvalds
2007-07-14 0:36 ` David Woodhouse
2007-07-14 0:44 ` J. Bruce Fields
2007-07-14 0:49 ` David Woodhouse
2007-07-14 1:29 ` Jakub Narebski
2007-07-14 13:23 ` Robin Rosenberg [this message]
2007-07-14 13:09 ` Julian Phillips
2007-07-14 22:22 ` Jan Hudec
2007-07-14 22:36 ` Julian Phillips
2007-07-15 1:46 ` Daniel Barkalow
2007-07-12 6:26 ` Eric Wong
2007-07-12 13:05 ` Randal L. Schwartz
2007-07-12 18:25 ` Eric Wong
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200707141523.32929.robin.rosenberg.lists@dewire.com \
--to=robin.rosenberg.lists@dewire.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=andyparkins@gmail.com \
--cc=bfields@fieldses.org \
--cc=bulb@ucw.cz \
--cc=dwmw2@infradead.org \
--cc=git@vger.kernel.org \
--cc=torvalds@linux-foundation.org \
--cc=tytso@mit.edu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).