git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: Linus Torvalds <torvalds@linux-foundation.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: Sat, 14 Jul 2007 00:46:54 +0100	[thread overview]
Message-ID: <1184370414.2785.79.camel@shinybook.infradead.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0707131617270.20061@woody.linux-foundation.org>

On Fri, 2007-07-13 at 16:18 -0700, Linus Torvalds wrote:
> 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. 

This is true. I already mirror a bunch of CVS and SVN repositories into
git so that I can use them without too much pain¹, and I can do the same
for git trees which use branches too; mirroring them into a bunch of
separate trees for easy access.

On the occasions I actually try to _use_ branches, I find it very
suboptimal. Perhaps it's just because I'm stupid. I'm sure that's why I
ended up committing changes to the wrong branch. But having to rebuild
(even with ccache) after changing branches is a PITA. Just changing
branches at all is a PITA if you have uncommitted changes (which I
usually do because I've usually tested _some_ random patch in a build
tree for the hardware which is closest to hand). Pulling a whole bunch
of unwanted changes on the 'development' branch while on GPRS, when all
I really needed was a single commit from the 'stable' branch also didn't
amuse me, although I'm sure if I had the time to play with it I'd have
been able to avoid that.

I can, and do, mirror stuff from all kinds of suboptimal version control
systems into single-branch git trees. And I include multi-branched git
trees in my definition of 'suboptimal'. My ability to do that doesn't
really help the newbies who are expected with branches, though.

I just wish people would make stuff available on the _servers_ in
separate trees rather than in branches -- if some people prefer branches
locally then that's their option; at the moment we kind of force people
into it. They _could_ avoid it but they'd have to know what they're
doing.

But I didn't really mean to start an argument; it's just my opinion.

-- 
dwmw2

¹ and I'd do the same for Hg if I could get hg2git to work.

  reply	other threads:[~2007-07-13 23:49 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 [this message]
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=1184370414.2785.79.camel@shinybook.infradead.org \
    --to=dwmw2@infradead.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=andyparkins@gmail.com \
    --cc=bulb@ucw.cz \
    --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).