git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Ping Yin" <pkufranky@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: "Theodore Ts'o" <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 13:48:33 +0800	[thread overview]
Message-ID: <46dff0320711112148u59d01ff4v4fea7168c9822799@mail.gmail.com> (raw)
In-Reply-To: <7vzlxk8apz.fsf@gitster.siamese.dyndns.org>

> I have a bit of reservation about revert, but I'd imagine we
> could kill it, and also fetch, pull and push, if you are
> shooting for *real* beginners who work alone.  I think the only
> valid justification to drop "revert" from the list is to assume
> that the audience do not interact with the outside world, and
> dropping fetch/pull/push from the list is in line with that.
many "real" beginners are users of CVS/svn, so the very first thing
they want to do is simulating the cvs/svn operation, so IMHO pull
(update) and push(commit) should be kept.
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>



-- 
Ping Yin

  reply	other threads:[~2007-11-12  5:48 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 [this message]
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
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=46dff0320711112148u59d01ff4v4fea7168c9822799@mail.gmail.com \
    --to=pkufranky@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --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).