From: Jon Loeliger <jdl@freescale.com>
To: "John J. Franey" <jjfraney@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: changing history once public
Date: Fri, 30 May 2008 16:37:19 -0500 [thread overview]
Message-ID: <4840738F.2070909@freescale.com> (raw)
In-Reply-To: <1212182690.8311.30.camel@isidore.myhome.westell.com>
John J. Franey wrote:
> I think I understand the issue with changing history on branches that
> have been made public.
>
> What is the negative of publishing a branch and not being able to apply
> history changing commands?
If there is something in that history you want to "remove",
it must be done as an inverse patch, or an additional "removal"
patch. You can't just change the history by backing it up and
writing it differently.
> If I want to keep this branch current (in public), I would pull from the
> tracking branch resolve conflicts and push to my public repo.
Right.
> This
> action leaves my commit as the parent of another commit; it is not
> longer at HEAD. Does it matter if my commit is no longer HEAD of my
> branch?
Uh, by definition HEAD is the current-most commit on your
active branch, right?
HTH,
jdl
prev parent reply other threads:[~2008-05-30 21:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-30 21:24 changing history once public John J. Franey
2008-05-30 21:37 ` Jon Loeliger [this message]
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=4840738F.2070909@freescale.com \
--to=jdl@freescale.com \
--cc=git@vger.kernel.org \
--cc=jjfraney@gmail.com \
/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).