From: Linus Torvalds <torvalds@linux-foundation.org>
To: David Woodhouse <dwmw2@infradead.org>
Cc: 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: Fri, 13 Jul 2007 16:18:03 -0700 (PDT) [thread overview]
Message-ID: <alpine.LFD.0.999.0707131617270.20061@woody.linux-foundation.org> (raw)
In-Reply-To: <1184367619.2785.58.camel@shinybook.infradead.org>
On Sat, 14 Jul 2007, David Woodhouse wrote:
>
> Branches just seem like a source of complexity and hence pain. Using git
> was just starting to become sensible for newbies, and now when people
> are forced to deal with multiple branches it's all horribly painful
> again.
Why would anybody force you to do that?
The "switch between branchs in the same repo" is really convenient. But
nobody *forces* you to do it.
Linus
next prev parent reply other threads:[~2007-07-13 23:18 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 [this message]
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
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=alpine.LFD.0.999.0707131617270.20061@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=Johannes.Schindelin@gmx.de \
--cc=andyparkins@gmail.com \
--cc=bulb@ucw.cz \
--cc=dwmw2@infradead.org \
--cc=git@vger.kernel.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).