From: Chris Frey <cdfrey@foursquare.net>
To: Joshua Jensen <jjensen@workspacewhiz.com>
Cc: weigelt@metux.de, git@vger.kernel.org
Subject: Re: Cutting history
Date: Sat, 10 Jul 2010 02:43:04 -0400 [thread overview]
Message-ID: <20100710064304.GA15600@foursquare.net> (raw)
In-Reply-To: <4C37F24E.30407@workspacewhiz.com>
On Fri, Jul 09, 2010 at 10:08:46PM -0600, Joshua Jensen wrote:
> Your post reminded me of this: http://progit.org/2010/03/17/replace.html
Wow. This is what I get for not following git development more closely. :-)
Doesn't this open a potential security problem? Suppose you want to pull
from another developer's repo, and he's replaced some of the history
in your own tree. According to the above article, it is possible to
share replacements, presumably like any other ref.
Is it possible to have your own branch history "replaced" by fetching
someone else's repo into a remote branch?
- Chris
next prev parent reply other threads:[~2010-07-10 6:54 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-10 3:25 Cutting history Enrico Weigelt
2010-07-10 4:08 ` Joshua Jensen
2010-07-10 6:43 ` Chris Frey [this message]
2010-07-10 8:47 ` Jakub Narebski
2010-07-10 10:40 ` Martin Pettersson
2010-07-10 11:58 ` Ævar Arnfjörð Bjarmason
2010-07-10 20:12 ` Ævar Arnfjörð Bjarmason
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=20100710064304.GA15600@foursquare.net \
--to=cdfrey@foursquare.net \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.com \
--cc=weigelt@metux.de \
/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.