unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: mathias@mnet-mail.de, sb@dod.no, emacs-devel@gnu.org
Subject: Re: Stash
Date: Mon, 06 Apr 2015 15:19:12 +0300	[thread overview]
Message-ID: <83384dla9r.fsf@gnu.org> (raw)
In-Reply-To: <CAP_d_8UAGe=VDbp7oZ4Tae7Lo7u51-gFQZ0Ajz=M8yjjxspTFA@mail.gmail.com>

> From: Yuri Khan <yuri.v.khan@gmail.com>
> Date: Mon, 6 Apr 2015 17:56:47 +0600
> Cc: Mathias Megyei <mathias@mnet-mail.de>, Steinar Bang <sb@dod.no>, 
> 	Emacs developers <emacs-devel@gnu.org>
> 
> On Mon, Apr 6, 2015 at 5:30 PM, Eli Zaretskii <eliz@gnu.org> wrote:
> 
> >> Is there a reason why you don't mention 'gitk' in GitQuickStartForEmacsDevs?
> >
> > I don't want to assume gitk is installed, nor that the Git commands
> > are invoked from a sufficiently capable terminal.
> 
> A git browser (especially a graphical, point-and-clicky one) is an
> immensely useful tool in understanding and learning Git. And gitk is
> the one that has the best chance of being installed, or easiest to
> install. (Most other git browsers are platform-specific.)
> 
> Alternatively, Emacs could include a git browser. (Magit already does;
> I don’t know about vc.)

All true, but most of that needs user actions to actually show the
diffs; by default they only show the SHA1 values and the DAG, which is
not what is needed here.  And even the DAG itself might be confusing
at times to someone uninitiated.

The instructions, by contrast, aim at being as clear and unequivocal
as possible.  There's nothing more irritating than a recipe that
doesn't work or cannot be followed or understood, particularly when
you are trying to get yourself out of some trouble you don't fully
understand.

> A git browser is most useful if directed to show not only the current
> branch but also the associated remote tracking branch, e.g. (assuming
> a POSIX shell):
> 
> $ gitk HEAD $(git rev-parse --symbolic-full-name @{u}) &

Yes, but all this is almost useless to someone who doesn't yet know
what a "remote tracking branch" is.  It will take time for the
audience of GitQuickStartForEmacsDevs to get there.




  parent reply	other threads:[~2015-04-06 12:19 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-05 17:42 Stash Richard Stallman
2015-04-05 18:31 ` Stash Steinar Bang
2015-04-05 18:38   ` Stash Eli Zaretskii
2015-04-06  5:50   ` Stash Richard Stallman
2015-04-06  6:37     ` Stash Steinar Bang
2015-04-06  7:35     ` Stash Eli Zaretskii
2015-04-06  7:57       ` Stash Eli Zaretskii
2015-04-07 19:31       ` Stash Stephen J. Turnbull
2015-04-08  5:28         ` Stash Eli Zaretskii
2015-04-06  5:50   ` Stash Richard Stallman
2015-04-06  6:50     ` Stash Steinar Bang
2015-04-06  6:55       ` Stash Eli Zaretskii
2015-04-06 11:25         ` Stash Mathias Megyei
2015-04-06 11:30           ` Stash Eli Zaretskii
2015-04-06 11:56             ` Stash Yuri Khan
2015-04-06 12:06               ` Stash João Távora
2015-04-06 12:25                 ` Stash Eli Zaretskii
2015-04-06 12:19               ` Eli Zaretskii [this message]
2015-04-06 11:59             ` Stash João Távora
2015-04-06 12:21               ` Stash Eli Zaretskii
2015-04-06 13:06                 ` Stash João Távora
2015-04-06  6:55       ` Stash Eli Zaretskii
2015-04-06 14:53       ` Stash Steinar Bang
2015-04-06 15:07         ` Stash Harald Hanche-Olsen
2015-04-06 18:48           ` Stash Steinar Bang
2015-04-06  5:51   ` Stash Richard Stallman
2015-04-06  7:29     ` Stash Eli Zaretskii
2015-04-06  7:55       ` Stash Harald Hanche-Olsen
2015-04-07 16:13       ` Stash Richard Stallman
2015-04-07 16:48         ` Stash Eli Zaretskii
2015-04-07 19:51           ` Stash Stephen J. Turnbull
2015-04-08 18:20             ` Stash Richard Stallman
2015-04-08 18:21           ` Stash Richard Stallman
2015-04-08 18:33             ` Stash Eli Zaretskii
2015-04-09 13:16               ` Stash Richard Stallman
2015-04-09 13:45                 ` Stash Eli Zaretskii
2015-04-10 10:57                   ` Stash Richard Stallman
2015-04-08 18:21           ` Stash Richard Stallman
2015-04-07 16:58         ` Stash Andreas Schwab
2015-04-08 18:21           ` Stash Richard Stallman
2015-04-09 17:07             ` Stash Andreas Schwab
2015-04-10 10:58               ` Stash Richard Stallman
2015-04-07 20:12     ` Stash Stephen J. Turnbull
2015-04-09 13:16       ` Stash Richard Stallman
2015-04-09 16:53         ` Stash Stephen J. Turnbull
2015-04-10 10:58           ` Stash Richard Stallman
2015-04-10 11:18             ` Stash Eli Zaretskii
2015-04-10 13:52             ` Stash Stephen J. Turnbull
2015-04-05 18:40 ` Stash Paul Eggert
2015-04-05 19:25   ` Stash Harald Hanche-Olsen
2015-04-05 19:59     ` Stash Paul Eggert
2015-04-05 19:26   ` Stash Steinar Bang
2015-04-05 20:18     ` Stash Stephen J. Turnbull
2015-04-05 19:41 ` Stash Harald Hanche-Olsen

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83384dla9r.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=mathias@mnet-mail.de \
    --cc=sb@dod.no \
    --cc=yuri.v.khan@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.
Code repositories for project(s) associated with this public inbox

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

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 read-only IMAP folder(s) and NNTP newsgroup(s).