emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <nicholas.dokos@hp.com>
To: Ivanov Dmitry <usr345@gmail.com>
Cc: Nick Dokos <nicholas.dokos@hp.com>, emacs-orgmode@gnu.org
Subject: Re: Re[2]: Re[2]: need detailed instructions for submitting the patch
Date: Tue, 10 Aug 2010 14:29:00 -0400	[thread overview]
Message-ID: <21263.1281464940@gamaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Ivanov Dmitry <usr345@gmail.com> of "Tue, 10 Aug 2010 22:14:22 +0400." <1645190369.20100810221422@gmail.com>

Ivanov Dmitry <usr345@gmail.com> wrote:

> Yes, Nick, I was asking about the git commands. Thanks. It seems, that
> creating a topic branch is more complicated, then simply editing the
> local master copy, creating a diff file and sending it to the mailing
> list. I think it should be used only in complicated cases.

I prefer to keep a pristine master branch and create lots of topics branches,
(most of which die a quick and merciful death.) It's not really hard to create
a branch and it keeps things *much* neater, so I would recommend that approach
even for simple changes.


  reply	other threads:[~2010-08-10 18:29 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 [this message]
2010-08-10 18:29                 ` Thomas S. Dye
2010-08-11  5:09                   ` ReRe[2]: " Noorul Islam K M
2010-08-11 22:16                 ` Re[2]: " 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:

  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=21263.1281464940@gamaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=usr345@gmail.com \


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