all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Lars Magne Ingebrigtsen <larsi@gnus.org>
Cc: David Kastrup <dak@gnu.org>, emacs-devel@gnu.org
Subject: Re: Cluttering the git tree
Date: Tue, 18 Nov 2014 00:14:41 +0100	[thread overview]
Message-ID: <87wq6tzafy.fsf@igel.home> (raw)
In-Reply-To: <m37fytigl8.fsf@stories.gnus.org> (Lars Magne Ingebrigtsen's message of "Mon, 17 Nov 2014 23:53:55 +0100")

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> David Kastrup <dak@gnu.org> writes:
>
>> Ulf Jasper <ulf.jasper@web.de> writes:
>>
>>> Hi all,
>>>
>>> I just noticed that I cluttered the git tree with my last commit.  All
>>> my intermediate commits which were supposed to be visible only to me
>>> suddenly appeared in the public repository.  Sorry!
>>>
>>> I'll study some tutorials before the next commit.  Promised.
>>
>> The only way _not_ to have intermediate commits be visible (short of
>> creating a diff and applying it as a single commit) is to prettify your
>> branch before merging.  git rebase -i is useful for that.
>
> Well, he could just say "git pull --rebase", right?

That doesn't clean up the intermediate commits, it just transplants
them.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."



  reply	other threads:[~2014-11-17 23:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-17 20:51 Cluttering the git tree Ulf Jasper
2014-11-17 22:36 ` David Kastrup
2014-11-17 22:53   ` Lars Magne Ingebrigtsen
2014-11-17 23:14     ` Andreas Schwab [this message]
2014-11-20  6:18       ` Rob Browning
2014-11-20  5:03 ` Bill Wohler
2014-11-20 17:42   ` Ulf Jasper
2014-11-20 18:27     ` Achim Gratz
2014-11-20 19:01       ` Ulf Jasper

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=87wq6tzafy.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=larsi@gnus.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

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.