From: "Shawn O. Pearce" <spearce@spearce.org>
To: "Randal L. Schwartz" <merlyn@stonehenge.com>
Cc: Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com>, git@vger.kernel.org
Subject: Re: Many gits are offline this week
Date: Sun, 7 Oct 2007 13:01:53 -0400 [thread overview]
Message-ID: <20071007170153.GX2137@spearce.org> (raw)
In-Reply-To: <86tzp54sez.fsf@blue.stonehenge.com>
"Randal L. Schwartz" <merlyn@stonehenge.com> wrote:
> >>>>> "Paolo" == Paolo Ciarrocchi <paolo.ciarrocchi@gmail.com> writes:
>
> Paolo> is there any material (slides, docs) you can share before the talks?
>
> I've had the slides reviewed by Smarter People Than Me on #git already, so
> hopefully most of it is accurate. :) They're temporarily at
>
> http://www.stonehenge.com/pic/Git-2.0.3-to-be.pdf
>
> I still hope to have a few hours to go in and add a few sadly missing
> graphics, particularly on the rebase vs merge section.
What, no mention of git-gui as a porcelain? It has more users
than qgit according to the survey. Maybe rephrase the porcelains
on slide 15 as:
Other porcelain exists:
- StGit ("stacked git"), guilt
- tig (curses-based viewer)
- qgit, git-gui
On slide 26 you say "gitk mytopic origin" shows the changes back to
the common ancestor. That's what "gitk mytopic...origin" would do.
Note the three dots instead of the space. The space will cause
gitk to show all history back to the beginning of time.
On slide 27 you say that you can rebase your changes on upstream
using "git-rebase origin/master master". That's a lot more
typing than is required, most people will want to rebase their
current branch onto the upstream and thus will use "git-rebase
origin/master". Personally I think combining git-checkout's branch
switch feature into git-rebase is stupid. It really makes things
confusing. But its supported. :-(
--
Shawn.
next prev parent reply other threads:[~2007-10-07 17:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-05 1:04 Many gits are offline this week Shawn O. Pearce
2007-10-05 1:27 ` Randal L. Schwartz
2007-10-05 1:36 ` Johannes Schindelin
2007-10-05 1:43 ` Shawn O. Pearce
2007-10-05 1:59 ` alan
2007-10-05 9:14 ` Paolo Ciarrocchi
2007-10-05 13:12 ` Randal L. Schwartz
2007-10-05 14:41 ` Dmitry Potapov
2007-10-05 16:20 ` David Brown
2007-10-05 17:19 ` Dmitry Potapov
2007-10-05 18:33 ` Jeff King
2007-10-07 17:01 ` Shawn O. Pearce [this message]
2007-10-07 19:04 ` Daniel Barkalow
2007-10-07 22:31 ` Johannes Schindelin
2007-10-07 23:09 ` Shawn O. Pearce
2007-10-07 19:37 ` Randal L. Schwartz
2007-10-28 10:07 ` Mike Hommey
2007-10-05 1:43 ` Johannes Schindelin
2007-10-07 4:59 ` Steven Grimm
2007-10-05 15:13 ` Frank Lichtenheld
2007-10-05 20:26 ` Pierre Habouzit
2007-10-06 9:05 ` Lars Hjemli
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=20071007170153.GX2137@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=merlyn@stonehenge.com \
--cc=paolo.ciarrocchi@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 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.