From: "Óscar Fuentes" <ofv@wanadoo.es>
To: emacs-devel@gnu.org
Subject: Re: DVCS workflow and bisect
Date: Thu, 21 Jan 2010 19:43:27 +0100 [thread overview]
Message-ID: <87my078fjk.fsf@telefonica.net> (raw)
In-Reply-To: 87my07beol.fsf@mithlond.arda
Teemu Likonen <tlikonen@iki.fi> writes:
[snip]
> My point is not to say that the author of the commit did any serious
> damage or anything. I'm just suggesting that merging stuff and making
> other changes should be separate commits.
Thanks for pointing this out.
This scenario is what Stephen was trying to avoid when he wrote the
documentation for the distributed worflow.
Please, guys, don't use any undocumented workflow unless you really
*know* what you are doing.
next prev parent reply other threads:[~2010-01-21 18:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-21 16:33 DVCS workflow and bisect Teemu Likonen
2010-01-21 18:43 ` Óscar Fuentes [this message]
2010-01-22 4:26 ` Stephen J. Turnbull
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=87my078fjk.fsf@telefonica.net \
--to=ofv@wanadoo.es \
--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).