All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Narebski <jnareb@gmail.com>
To: Johannes.Schindelin@gmx.de
Cc: msysgit@googlegroups.com, git@vger.kernel.org
Subject: Re: The 8th airing of the msysGit herald
Date: Sun, 02 Mar 2008 16:44:58 -0800 (PST)	[thread overview]
Message-ID: <m34pbok54h.fsf@localhost.localdomain> (raw)
In-Reply-To: <alpine.LSU.1.00.0803022329560.22527@racer.site>


Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

> > 4) What do you hate most in Git? 
> 
> The command line options. Sometimes it seems to me all the really cool 
> actions in git can only be invoked by a mysterious collection of weird 
> option switches which 1. I've never heard of, 2. are hidden deep down 
> in long manual pages which make it impossible to distinguish important 
> options from the unimportant ones, and 3. change very frequently in 
> new versions. For example, "git rebase -i" is a nice feature, but it 
> is simply a different action than a one-shot "git rebase". Hence, if 
> it is supposed to be really used, it should rather be a command such 
> as "git interactive-rebase". The GUI tools go a long way to hide those 
> mysterious option collections, but some of the daily workflow steps 
> are still unavailable in the GUI. Rebase being the most prominent, I 
> guess. 

It is not that much different. The basis operation is the same;
I don't think that "rebase -i" differs from "rebase" more than
"add -i" differs from "add".

> > 6) What was the most frustrating moment when working with Git? 
> 
> Finding that "git pull" will create many more merge commits than I 
> wanted, and that there doesn't seem to be an easy way of running "git 
> fetch; git rebase" in one command.

"git pull --rebase", but it is quite new feature.

-- 
Jakub Narebski
Poland
ShadeHawk on #git

  reply	other threads:[~2008-03-03  0:45 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-02 23:30 The 8th airing of the msysGit herald Johannes Schindelin
2008-03-03  0:44 ` Jakub Narebski [this message]
2008-03-03  0:54   ` Johannes Schindelin
2008-03-03  1:10     ` Jakub Narebski
2008-03-03 12:00       ` Tilman Schmidt
2008-03-03 12:05         ` Johannes Schindelin
2008-03-03 18:21           ` Tilman Schmidt
2008-03-03 18:48             ` Brandon Casey
2008-03-05 23:12               ` Tilman Schmidt
2008-03-03 17:18         ` Junio C Hamano
2008-03-03 18:27           ` Tilman Schmidt
2008-03-03 22:37             ` Junio C Hamano
2008-03-03 22:58               ` Martin Langhoff
2008-03-05 23:40                 ` Tilman Schmidt
2008-03-06  0:26                   ` Johannes Schindelin
2008-03-06  0:41                     ` Junio C Hamano
2008-03-06  2:03                       ` Jim Raden
2008-03-06  2:29                         ` Johannes Schindelin
2008-03-06  2:42                           ` Jim Raden
2008-03-06  4:32                             ` [msysGit] " Jay Soffian
2008-03-06  4:33                               ` Jim Raden
2008-03-06 11:40                                 ` [msysGit] " Paul Franz
2008-03-06  4:29                   ` Jay Soffian

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=m34pbok54h.fsf@localhost.localdomain \
    --to=jnareb@gmail.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=msysgit@googlegroups.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.