From: Rich Pixley <rich.pixley@palm.com>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: Sitaram Chamarty <sitaramc@gmail.com>, "Ted Ts'o" <tytso@mit.edu>,
Seth Robertson <in-gitvger@baka.org>,
"git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Newbie grief
Date: Tue, 01 May 2012 14:29:52 -0700 [thread overview]
Message-ID: <4FA055D0.7040102@palm.com> (raw)
In-Reply-To: <86mx5rmx32.fsf@red.stonehenge.com>
On 5/1/12 14:05 , Randal L. Schwartz wrote:
>>>>>> "Rich" == Rich Pixley<rich.pixley@palm.com> writes:
>
> Rich> I want to be able to fetch changes to the branch I currently have checked out.
> Rich> Git blocks this because it doesn't know how to cope with the working directory
> Rich> in that situation.
>
> It does?
Yes, it does.
> I can always "git fetch origin" in my repo, and the remote
> branches are in "origin/master, origin/foo, origin/bar". Totally
> separate from my working tree.
Sure. You can fetch other branches, (unless you happen to be checked
out from them). But you can't fetch to master if you're checked out
from master.
> So, make a set of related names for your branches. It's better with
> names anyway.
I disagree. They only even need branches if they're different. And the
branches can be extremely lightweight. With names, I have to manually
track a geometric explosion of extraneous branches and branch names,
just in order to be able to sync changes back and forth. That's all
work that could be managed automatically by the source code control system.
> Rich> Pushing is blocked in git. Git simply refuses some push requests
> Rich> which have obvious and fairly straightforward semantics.
>
> git push master:from-merlyn/master
>
> And now someone can look at "from-merlyn/master", and know that it's
> from me, and related to master, and either incorporate it into the real
> master, or cherry-pick from it, or whatever. Solved.
Again, yes, you can push to other branches. You could push to other
repositories too. That's not really what I'm talking about.
> You're asking a lot of an automated system. I think you're trying to
> get a system to replace the communication you should be doing as a
> developer.
I hear that that's what you think. But really, I'm asking for
automation to replace the automation I already have in preexisting
source code control systems.
There are a number of situations, like the ones I've described, that git
just plain doesn't cope well with. Other source code control systems
have, and going backwards seems silly and frustrating.
My particular situation is that I'm developing a "feature" and to do
that, I need to be testing on multiple machines. Tens of them. I
really don't want hundreds of named branches that I must manually merge
from constantly.
With mercurial or monotone or even subversion, it's trivial. Branches
can be shared. And pushing between them is similarly trivial. It can
be done in seconds. With git, it takes hours to do all the manual
moves, track the manual moves manually, verify that they've been done
correctly, and then later it takes hours to correct the ones that were
done incorrectly because they were all done manually or because one
machine happened to be down at the time and so got the changes in the
wrong order, or whatever.
I'm not asking for anything new. I'm asking for something that's as
capable as what we've had for years now.
--rich
next prev parent reply other threads:[~2012-05-01 21:29 UTC|newest]
Thread overview: 100+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 22:30 Newbie grief Rich Pixley
2012-04-30 23:31 ` Seth Robertson
2012-05-01 1:15 ` Rich Pixley
2012-05-01 1:32 ` Junio C Hamano
2012-05-01 1:55 ` Rich Pixley
2012-05-01 3:44 ` Sitaram Chamarty
2012-05-01 11:14 ` Ted Ts'o
2012-05-01 16:13 ` Sitaram Chamarty
2012-05-01 18:15 ` Rich Pixley
2012-05-01 18:20 ` Michael Witten
2012-05-01 18:52 ` Rich Pixley
2012-05-02 21:28 ` Jakub Narebski
2012-05-01 18:42 ` Randal L. Schwartz
2012-05-01 20:52 ` Rich Pixley
2012-05-01 21:05 ` Randal L. Schwartz
2012-05-01 21:12 ` Junio C Hamano
2012-05-01 21:25 ` Rich Pixley
2012-05-01 21:28 ` Randal L. Schwartz
2012-05-01 21:57 ` Rich Pixley
2012-05-01 22:56 ` Michael Witten
2012-05-01 23:55 ` Philip Oakley
2012-05-03 16:08 ` Hallvard Breien Furuseth
2012-05-03 18:20 ` Rich Pixley
2012-05-03 23:04 ` Hallvard Breien Furuseth
2012-05-03 23:06 ` Hallvard Breien Furuseth
2012-05-03 18:46 ` Rich Pixley
2012-05-03 21:09 ` Junio C Hamano
2012-05-03 22:44 ` Rich Pixley
2012-05-03 22:53 ` Randal L. Schwartz
2012-05-03 22:59 ` Junio C Hamano
2012-05-04 19:23 ` Felipe Contreras
2012-05-04 19:30 ` Felipe Contreras
2012-05-04 19:41 ` Michael Witten
2012-05-01 21:29 ` Rich Pixley [this message]
2012-05-01 21:39 ` Randal L. Schwartz
2012-05-01 22:07 ` Rich Pixley
2012-05-01 22:17 ` Andreas Ericsson
2012-05-01 23:01 ` PJ Weisberg
2012-05-03 18:43 ` Rich Pixley
2012-05-03 19:09 ` Nathan Gray
2012-05-03 19:16 ` Rich Pixley
2012-05-03 20:14 ` Randal L. Schwartz
2012-05-03 20:52 ` Rich Pixley
2012-05-04 15:56 ` Mark Brown
2012-05-04 18:23 ` Rich Pixley
2012-05-04 19:14 ` Jakub Narebski
2012-05-04 20:00 ` Mark Brown
2012-05-02 14:21 ` Hallvard Breien Furuseth
2012-05-02 15:21 ` Michael Witten
2012-05-03 12:23 ` Hallvard Breien Furuseth
2012-05-03 12:53 ` Randal L. Schwartz
2012-05-03 16:09 ` Michael Witten
2012-05-03 16:20 ` Hallvard Breien Furuseth
2012-05-03 16:44 ` Michael Witten
2012-05-03 18:26 ` Rich Pixley
2012-05-03 19:33 ` Ted Ts'o
2012-05-01 23:30 ` Felipe Contreras
2012-05-03 18:31 ` Rich Pixley
2012-05-03 18:58 ` Rich Pixley
2012-05-04 14:09 ` Andreas Ericsson
2012-05-04 14:59 ` Stephen Bash
2012-05-04 16:29 ` Mark Brown
2012-05-04 19:13 ` Felipe Contreras
2012-05-01 18:03 ` Rich Pixley
[not found] ` <4FA01C73.5000909@palm.com>
2012-05-02 0:44 ` Sitaram Chamarty
[not found] ` <4F9F28F5.2020403@palm.com>
2012-05-01 1:37 ` Seth Robertson
2012-05-01 3:04 ` Rich Pixley
2012-05-01 5:32 ` Michael Witten
2012-05-01 6:21 ` Junio C Hamano
2012-05-01 6:24 ` Michael Witten
2012-05-01 17:29 ` Rich Pixley
2012-05-01 17:33 ` Rich Pixley
2012-05-03 19:13 ` Rich Pixley
2012-05-03 20:19 ` Ronan Keryell
2012-05-03 21:13 ` Junio C Hamano
2012-05-03 22:23 ` Ronan Keryell
2012-05-03 22:33 ` Rich Pixley
2012-05-03 22:39 ` Rich Pixley
2012-05-04 1:01 ` Illia Bobyr
2012-05-04 3:13 ` Nathan Gray
2012-05-04 4:35 ` Michael Witten
2012-05-04 5:25 ` Junio C Hamano
2012-05-04 10:09 ` Carlos Martín Nieto
2012-05-04 14:50 ` Junio C Hamano
2012-05-04 17:39 ` Junio C Hamano
2012-05-04 16:46 ` Nathan Gray
2012-05-04 17:17 ` Illia Bobyr
2012-05-04 18:10 ` Rich Pixley
2012-05-04 17:57 ` Rich Pixley
2012-05-04 19:22 ` Michael Witten
2012-05-04 19:18 ` Andrew Sayers
2012-05-04 18:57 ` Jérôme Benoit
2012-05-04 20:03 ` Felipe Contreras
2012-05-04 20:27 ` Junio C Hamano
2012-05-04 20:45 ` Felipe Contreras
2012-05-04 21:29 ` Rich Pixley
2012-05-04 22:05 ` Felipe Contreras
2012-04-30 23:35 ` Jan Krüger
2012-05-01 18:59 ` Rich Pixley
2012-05-02 8:25 ` Philippe Vaucher
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=4FA055D0.7040102@palm.com \
--to=rich.pixley@palm.com \
--cc=git@vger.kernel.org \
--cc=in-gitvger@baka.org \
--cc=merlyn@stonehenge.com \
--cc=sitaramc@gmail.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.