emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Noorul Islam K M <noorul@noorul.com>
To: "Thomas S. Dye" <tsd@tsdye.com>
Cc: Nick Dokos <nicholas.dokos@hp.com>,
	emacs-orgmode@gnu.org, Ivanov Dmitry <usr345@gmail.com>
Subject: Re: ReRe[2]: need detailed instructions for submitting the patch
Date: Wed, 11 Aug 2010 10:39:21 +0530	[thread overview]
Message-ID: <87zkwtka66.fsf@noorul.maa.corp.collab.net> (raw)
In-Reply-To: <7337F995-8B14-4BB9-8E37-52FBEA74F760@tsdye.com> (Thomas S. Dye's message of "Tue, 10 Aug 2010 08:29:30 -1000")

"Thomas S. Dye" <tsd@tsdye.com> writes:

> Aloha Dmitry,
>
> Another reason for working in topic branches is it leaves your master
> branch clean so that changes in the remote are easily merged.  You're
> are probably more computer savvy than I am, but my struggles with
> merges after making changes to the master branch have been trying.  I
> try to leave master clean at all times now.
>

I would like to try this approach. I have been finding it very hard to
maintain the master branch with the other approach.

Thanks
Noorul

next prev parent reply	other threads:[~2010-08-11  5:10 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-09 21:59 need detailed instructions for submitting the patch Ivanov Dmitry
2010-08-09 23:36 ` Juan
2010-08-10  0:55   ` Bernt Hansen
2010-08-10 15:00     ` Re[2]: " Ivanov Dmitry
2010-08-10 15:30       ` Bastien
2010-08-10 17:33         ` Re[2]: " Ivanov Dmitry
2010-08-10 17:47           ` Bastien
2010-08-10 17:57             ` Nick Dokos
2010-08-10 18:11               ` Dan Davison
2010-08-10 20:39                 ` David Maus
2010-08-10 18:14               ` Re[2]: Re[2]: " Ivanov Dmitry
2010-08-10 18:29                 ` Nick Dokos
2010-08-10 18:29                 ` Thomas S. Dye
2010-08-11  5:09                   ` Noorul Islam K M [this message]
2010-08-11 22:16                 ` Bastien
2010-08-11 23:00               ` Bastien
2010-08-10 15:34       ` Eric Schulte

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.orgmode.org/

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

  git send-email \
    --in-reply-to=87zkwtka66.fsf@noorul.maa.corp.collab.net \
    --to=noorul@noorul.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=nicholas.dokos@hp.com \
    --cc=tsd@tsdye.com \
    --cc=usr345@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

Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.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).