From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Mike Hommey <mh@glandium.org>
Cc: Junio C Hamano <gitster@pobox.com>, Theodore Tso <tytso@mit.edu>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH,RFC 1/2] Make the list of common commands more exclusive
Date: Mon, 12 Nov 2007 12:23:38 +0000 (GMT) [thread overview]
Message-ID: <Pine.LNX.4.64.0711121222310.4362@racer.site> (raw)
In-Reply-To: <20071112102412.GA24803@glandium.org>
Hi,
On Mon, 12 Nov 2007, Mike Hommey wrote:
> On Sun, Nov 11, 2007 at 11:26:10PM -0800, Junio C Hamano <gitster@pobox.com> wrote:
> > > My mental model for git newbies is that they would probably be pulling
> > > from upstream repositories (so I was tempted to remove git-init from
> > > the common commands list), but they would rarely be cherry-picking or
> > > reverting other people's changes.
> >
> > I'd agree with that, but reverting and cherry-picking would also
> > be done on the commits the user builds on top of other people's
> > changes.
>
> On the other hand, cherry-picking and reverting are just the same thing,
> except one applies a reversed patch. Wouldn't it make sense to merge
> these two in one command ?
Technically, they are. That's why both of them live in builtin-revert.c.
But conceptually, they are not. At least _I_ found it hard at first, to
accept that reverting a patch really was a reverse cherry-picking.
Ciao,
Dscho
next prev parent reply other threads:[~2007-11-12 12:24 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 23:11 Deprecate git-fetch-pack? Daniel Barkalow
2007-11-11 0:48 ` Junio C Hamano
2007-11-11 3:09 ` Ask Bjørn Hansen
2007-11-11 11:05 ` Johannes Schindelin
2007-11-11 21:16 ` Junio C Hamano
2007-11-11 22:21 ` Theodore Tso
2007-11-11 22:35 ` Junio C Hamano
2007-11-11 22:50 ` Johannes Schindelin
2007-11-11 23:58 ` Theodore Tso
2007-11-12 0:16 ` Jakub Narebski
2007-11-12 17:29 ` Jon Loeliger
2007-11-12 17:33 ` Johannes Schindelin
2007-11-12 18:56 ` Jon Loeliger
2007-11-12 19:08 ` Johannes Schindelin
2007-11-12 19:16 ` Jon Loeliger
2007-11-12 0:57 ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Theodore Ts'o
2007-11-12 0:57 ` [PATCH,RFC 2/2] Remove hint to use "git help -a" Theodore Ts'o
2007-11-12 2:21 ` [PATCH,RFC 1/2] Make the list of common commands more exclusive Junio C Hamano
2007-11-12 5:48 ` Ping Yin
2007-11-12 6:22 ` Theodore Tso
2007-11-12 7:26 ` Junio C Hamano
2007-11-12 10:24 ` Mike Hommey
2007-11-12 12:23 ` Johannes Schindelin [this message]
2007-11-12 7:57 ` Ask Bjørn Hansen
2007-11-12 10:21 ` Andreas Ericsson
2007-11-12 15:20 ` Theodore Tso
2007-11-12 10:15 ` Deprecate git-fetch-pack? Andreas Ericsson
2007-11-12 1:10 ` Ask Bjørn Hansen
2007-11-11 8:32 ` Mike Hommey
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=Pine.LNX.4.64.0711121222310.4362@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mh@glandium.org \
--cc=tytso@mit.edu \
/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).