From: "Thomas S. Dye" <firstname.lastname@example.org> To: Ivanov Dmitry <email@example.com> Cc: Nick Dokos <firstname.lastname@example.org>, email@example.com Subject: Re: Re: Re: need detailed instructions for submitting the patch Date: Tue, 10 Aug 2010 08:29:30 -1000 [thread overview] Message-ID: <7337F995-8B14-4BB9-8E37-52FBEA74F760@tsdye.com> (raw) In-Reply-To: <firstname.lastname@example.org> 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. All the best, Tom On Aug 10, 2010, at 8:14 AM, Ivanov Dmitry 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. > > Dmitry > > > _______________________________________________ > Emacs-orgmode mailing list > Please use `Reply All' to send replies to the list. > Emacsemail@example.com > http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next prev parent 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 Ivanov Dmitry 2010-08-09 23:36 ` Juan 2010-08-10 0:55 ` Bernt Hansen 2010-08-10 15:00 ` Re: " Ivanov Dmitry 2010-08-10 15:30 ` Bastien 2010-08-10 17:33 ` Re: " 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: Re: " Ivanov Dmitry 2010-08-10 18:29 ` Nick Dokos 2010-08-10 18:29 ` Thomas S. Dye [this message] 2010-08-11 5:09 ` ReRe: " Noorul Islam K M 2010-08-11 22:16 ` Re: " 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=7337F995-8B14-4BB9-8E37-52FBEA74F760@tsdye.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Re: Re: need detailed instructions for submitting the patch' \ /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 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).