emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@altern.org>
To: Jarmo Hurri <jarmo.hurri@syk.fi>
Cc: emacs-orgmode@gnu.org
Subject: Re: Sending commits to Org
Date: Sun, 23 Sep 2012 09:21:25 +0200	[thread overview]
Message-ID: <87d31dtdai.fsf@bzg.ath.cx> (raw)
In-Reply-To: <87ipb6x7m1.fsf@syk.fi> (Jarmo Hurri's message of "Sat, 22 Sep 2012 20:58:14 +0300")

Hi Jarmo,

Jarmo Hurri <jarmo.hurri@syk.fi> writes:

> Or, if you are a git newbie like me, and fail to read the relevant part
> of the org page on contributing, and make your changes in the original
> master, you can also create patches from the original master branch
> using the HEAD identifier.

You should try to always edit from a dedicated branch.

If you commit something in master and want to discard this
commit later on, you will end up in trouble.  

Git makes it really easy to deal with branch.  I found this
short and useful video:




      reply	other threads:[~2012-09-23  7:21 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-20 11:40 Sending commits to Org Sebastien Vauban
2012-09-20 17:07 ` Philipp Kroos
2012-09-22 17:58   ` Jarmo Hurri
2012-09-23  7:21     ` Bastien [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:

  List information: https://www.orgmode.org/

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

  git send-email \
    --in-reply-to=87d31dtdai.fsf@bzg.ath.cx \
    --to=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=jarmo.hurri@syk.fi \


* 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


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).