unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Bill Wohler <wohler@newt.com>
To: emacs-devel@gnu.org
Subject: Re: need help adjusting workflow to git (or vice versa)
Date: Sun, 16 Nov 2014 10:57:31 -0800	[thread overview]
Message-ID: <874mtz0y90.fsf@olgas.newt.com> (raw)
In-Reply-To: 87lhncayq4.fsf@rosalinde.fritz.box

Stephen Berman <stephen.berman@gmx.net> writes:

> On Fri, 14 Nov 2014 07:26:19 +0200 Eli Zaretskii <eliz@gnu.org> wrote:
>
>> Every VCS has its downsides.  Bzr had only separate branches
>> (co-located branches were initially implemented in the last version);
>> git has only co-located branches.  You need to work around that.
>
> Yes, there's lots to learn and get used to.

I'd suggest reading Conversational Git [1] for a gentle introduction and Pro
Git [2] for a deeper dive (especially the chapter on branching).

1. http://blog.anvard.org/conversational-git/
2. http://git-scm.com/book/en/v2

-- 
Bill Wohler <wohler@newt.com> aka <Bill.Wohler@nasa.gov>
http://www.newt.com/wohler/
GnuPG ID:610BD9AD




  reply	other threads:[~2014-11-16 18:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-13 15:35 need help adjusting workflow to git (or vice versa) Stephen Berman
2014-11-13 15:49 ` Kelvin White
2014-11-13 19:50   ` Stephen Berman
2014-11-13 20:53     ` Kelvin White
2014-11-13 16:29 ` martin rudalics
2014-11-13 16:43   ` Andreas Schwab
2014-11-13 19:51     ` Stephen Berman
2014-11-13 20:10       ` Paul Eggert
2014-11-13 20:44         ` Stephen Berman
2014-11-13 20:58           ` Paul Eggert
2014-11-13 21:19             ` Stephen Berman
2014-11-13 20:58           ` Harald Hanche-Olsen
2014-11-13 21:22           ` Stefan Monnier
2014-11-14  5:26           ` Eli Zaretskii
2014-11-15 22:24             ` Stephen Berman
2014-11-16 18:57               ` Bill Wohler [this message]
2014-11-14  5:18       ` Rob Browning
2014-11-18  9:34         ` Eric S Fraga
2014-11-15  5:08       ` Bill Wohler

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=874mtz0y90.fsf@olgas.newt.com \
    --to=wohler@newt.com \
    --cc=emacs-devel@gnu.org \
    /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).