From: Linus Torvalds <torvalds@osdl.org>
To: James Bottomley <James.Bottomley@SteelEye.com>
Cc: git@vger.kernel.org, SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: SCSI trees, merges and git status
Date: Mon, 18 Apr 2005 17:29:24 -0700 (PDT) [thread overview]
Message-ID: <Pine.LNX.4.58.0504181724170.15725@ppc970.osdl.org> (raw)
In-Reply-To: <1113869594.4998.103.camel@mulgrave>
On Mon, 18 Apr 2005, James Bottomley wrote:
>
> Then the git-pull... script actually does the merge and the resulting
> tree checks out against BK
So?
What do you intend to do with all the other stuff I've already put on top?
Yes, I can undo my tree, but my tree has had more stuff in it since I
pulled from you, so not only will that confuse everybody who already got
the up-to-date tree, it will also undo stuff that was correct.
In other words, HISTORY CANNOT BE UNDONE.
That's the rule, and it's a damn good one. It was the rule when we used
BK, and it's the rule now. The fact that you can undo your history in
_your_ tree doesn't change anything at all.
So I can merge with your new tree, but that won't actually help any: I'll
just get a superset, the way you did things.
The way to remove patches is to explicitly revert them (effectively
applying a reverse diff), but I'm wondering if it's worth it in this case.
I looked at the patches I did get, and they didn't look horribly bad per
se. Are they dangerous?
2.6.12 is some time away, if for no other reason than the fact that this
SCM thing has obviously eaten two weeks of my time. So I'd be inclined to
chalk this up as a "learning experience" with git, and just go forward.
Linus
next prev parent reply other threads:[~2005-04-19 0:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-18 20:28 SCSI trees, merges and git status James Bottomley
2005-04-18 21:39 ` Linus Torvalds
2005-04-18 23:14 ` James Bottomley
2005-04-19 0:03 ` Linus Torvalds
2005-04-19 0:10 ` David Woodhouse
2005-04-19 0:16 ` James Bottomley
2005-04-19 0:41 ` David Woodhouse
2005-04-19 0:13 ` James Bottomley
2005-04-19 0:29 ` Linus Torvalds [this message]
2005-04-19 2:17 ` James Bottomley
2005-04-19 3:04 ` Linus Torvalds
2005-04-18 23:23 ` Junio C Hamano
2005-04-18 23:28 ` Petr Baudis
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.4.58.0504181724170.15725@ppc970.osdl.org \
--to=torvalds@osdl.org \
--cc=James.Bottomley@SteelEye.com \
--cc=git@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).