all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Nicolas Richard <theonewiththeevillook@yahoo.fr>
Cc: schwab@suse.de, emacs-devel@gnu.org
Subject: Re: Both 'master' and 'trunk'?
Date: Fri, 14 Nov 2014 12:23:50 +0200	[thread overview]
Message-ID: <83ppcqhyh5.fsf@gnu.org> (raw)
In-Reply-To: <5465D300.1040809@yahoo.fr>

> Date: Fri, 14 Nov 2014 11:01:36 +0100
> From: Nicolas Richard <theonewiththeevillook@yahoo.fr>
> CC: schwab@suse.de, emacs-devel@gnu.org
> 
> Le 14/11/2014 06:27, Eli Zaretskii a écrit :
> > Ah, okay.  It's indeed "origin".
> 
> FWIW I just realized that I like this presentation of git concepts :
> http://gitolite.com/gcs.html
> because it's short and focuses on ideas. That also means it won't get
> you started if you want to do things and know nothing, but my guess is
> that you already know the basic git commit/pull/push stuff.

Thanks.  However, concepts presented at this level are not my problem
where I am now.  The problem for me is to associate the terminology
(which is perverse at times, and seems to be deliberately invented to
confuse and trip someone who comes from another VCS) with the muscle
memory of the daily workflows.




      reply	other threads:[~2014-11-14 10:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 15:03 Both 'master' and 'trunk'? Eli Zaretskii
2014-11-13 15:47 ` Andreas Schwab
2014-11-13 16:19   ` Eli Zaretskii
2014-11-13 16:26     ` Andreas Schwab
2014-11-13 17:21       ` Eli Zaretskii
2014-11-13 16:29     ` Nicolas Richard
2014-11-13 17:15       ` Eli Zaretskii
2014-11-13 20:54         ` Nicolas Richard
2014-11-14  5:27           ` Eli Zaretskii
2014-11-14 10:01             ` Nicolas Richard
2014-11-14 10:23               ` Eli Zaretskii [this message]

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=83ppcqhyh5.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=schwab@suse.de \
    --cc=theonewiththeevillook@yahoo.fr \
    /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 external index

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

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.